Skip to Content
author's profile photo Former Member
Former Member

Load balancing question

I have a question about the SAP J2EE Load Balancing. To use Load balancing I want to change the “LoadbalancingPower” Parameter regulary.

In SAP docu I found the following sentences:

“To enable the changes to take effect, choose (Save Properties) on the toolbar and restart the Service Manager.”

Does anybody know how to restart the service Manager without restart the whole server?

Best regards

Nils Kloth

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 17, 2005 at 07:36 AM

    Hi Nils,

    guess you're refering to J2EE Engine 6.20, right?

    unfortunately, restarting the service manager only is not possible. The reason for this is that this Manager is a core component, and a lot of server components (the services) depend on it. Therefore, restarting the manager will trigger restart of the services as well, hence the restart of the server is necessary.

    Hope that explains it a bit.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Nils,

      You are basically trying to achieve hot deployment of your application. This is not possible currently with a single cluster.

      Changing the loadbalancing power of a node is not the right way to switch it off from the http loadbalancing.

      Instead if you want to exclude a node from the loadbalancing, you should:

      1. telnet to the Engine

      2. jump to the respective application node

      3. type suspend

      If you want later to add it back to the loadbalancing, then

      1. telnet to the Engine

      2. jump to the respective application node

      3. type resume

      However, this will not help you to achieve hot deployment.

      The reason is that:

      1. Deployment is clusterwide - that is you are deploying on first on the state controller, then all active application nodes synchronize from it.

      2. During deployment the application is stopped, clusterwide.

      3. When an application node joins the cluster it synchronizes applications from the state controller to get the currently operational version. So even if you somehow succeed in deploying a different version on the application node (for example by running it with a different cluster where you perform deployment), when it joins the cluster, this inconsistency will be removed and it will get again the old, currently active version of the application.

      I hope this was helpful.

      Best Regards: Iavor

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.