Page History

...

<configuration name="geronimo/tomcat/1.0/car">
<gbean name="TomcatResources">
</gbean>
+ <gbean name="TomcatEngine">
+ <attribute name="initParams">
+ name=Geronimo
+ jvmRoute=node98
+ </attribute>
+ </gbean>
<gbean name="TomcatWebConnector">
<attribute name="host">0.0.0.0</attribute>
<attribute name="port">8080</attribute>
<attribute name="redirectPort">8443</attribute>
</gbean>

For Geronimo v1, you should specify the jvmRoute on the cmdline when the server is started.

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

nodeX should have a unique value for each geronimo cluster member

In the near future, the jvmRoute attribute will be configurable via the var/config/config.xml file.

Go ahead and start the geronimo server on each cluster member now specifying the correct jvmRoute value.

Remember that the jvmRoute value must be unique for each cluster member and the server must be stopped when updating config.xml.

Now start the geronimo server (e.g. bin/geronimo.bat|sh run) and Now that the jvmRoute is set correctly for each cluster member. You should 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.

...