Page History

...

Each geronimo cluster member must have a unique jvmRoute designation for both load balancing and session replication.
In the near future, the jvmRoute attribute will be configurable via the var/config/config.xml file. Unfortunately, the only current way to setup the jvmRoute is by rebuilding the geronimo server for each cluster member. The jvmRoute should be configured with a unique value for each cluster member as shown below:

Update filename: geronimo/configs/tomcat/src/plan/plan.xml as follows

<gbean name="TomcatEngine" class="org.apache.geronimo.tomcat.EngineGBean">
<attribute name="className">org.apache.geronimo.tomcat.TomcatEngine</attribute>
<attribute name="initParams">
name=Geronimo
jvmRoute=nodex
</attribute>

For Geronimo v1, you need to specify the jvmRoute when the server is started.

Specifically, java -DjvmRoute=nodeX -jar bin/server.jar

nodeX should have a unique value for each geronimo cluster member You must rebuild geronimo and uncompress the resulting image for the cluster member. Repeat the procedure for the next cluster member while assuring that a different jvmRoute value is used. Instructions for rebuilding geronimo is beyond the scope of this article. These instructions are available on the Geronimo Wiki at http://geronimo.apache.org^{Image Removed} and in the archives of the mailing lists.

Now that the jvmRoute is set correctly for each cluster member. You must deploy the example on each of the cluster members. For this example, the applications are slightly different for each cluster member. The difference is merely to indicate the current Server number (e.g. Server 1, Server 2) in the output of the application. This will be useful when trying to determine which cluster member is servicing the http request from the browser.

...