Skip to Content
avatar image
Former Member

controlling which JVM is used in a load balanced environment?

we are trying to track down some intermittent problems in our load balanced Netweaver 2004s environment. One of the things we want to do is to be able to run a servlet on a particular engine in that environment (or run it 8 times, once on each engine).

How can we ensure which engine a particular request gets executed on?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 18, 2008 at 01:50 PM

    First isolate the instance and access it directly

    http://<host>:<port>/.....

    If you have multiple server nodes (server0, server1, etc.) on that instance, stop them first.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi!

      Interesting to know...

      for these numbers: They are the NodeIDs of your java nodes it seems...

      the one with '00' at the end is the dispatcher, '50' would be server0, '51' server1 and so on...

      You can find them in visual Admin or configtool or when you look at your logfiles.

      Good luck in troubleshooting...

      Jörg

  • avatar image
    Former Member
    Mar 20, 2008 at 12:52 PM

    Hi!

    As mentioned before, to directy access a 'instance' instance (meaning dialog instance) is easy by specifying the combination. To access an individual servernode (which you seemingly want to) is definitely not so easy. Could you elaborate on WHY you need to know on which servernode the servlet gets executed? One way to try and move in that direction is to 'undeploy' the servlet via the deploy service in visual Admin from all servernodes but the one you're interested in. I am not sure if that works though.

    Regards,

    Jörg

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Here's why I need to do this:

      I have one (or perhaps a couple) of server nodes that are having their default language changed. They seem to start with en_US, but somewhere along the lines, it's getting changed to pt_BR.

      We are working on finding what application we have deployed that has caused the problem, but that is looking to be a time-consuming operation.

      In the interim, it would be good to be able to periodically run a script that checks the current default language on each of the server nodes (and perhaps set it back).