FWIW, I am in the process of migrating to 3.2.4. I currently use maven to generate our
new server instances and have been using token replacement for this particular
property up to now.
I've employed a system property strategy (-Dtomcat.id with corresponding edits to the
tomcat server.xml file) for the jvmRoute and thought I would test your idea to do the
same with the cluster partition name. I made the following edits in my test
environment:
in deploy/cluster-service.xml:
| changed :
| <attribute name="PartitionName">DefaultPartition</attribute>
|
| to:
| <attribute name="PartitionName">${partition.name}</attribute>
|
and in deploy/jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/META-INF/jboss.web
| changed:
| <cluster-config>
| <partition-name>DefaultPartition</partition-name>
| </cluster-config>
|
| to:
| <cluster-config>
| <partition-name>${partition.name}</partition-name>
| </cluster-config>
|
Then I passed in -Dpartition.name to the startup. This had the expected results -- the
cluster was setup with the passed in name.
These are the only clustered services installed in my test server, but I assume the
same would work for others.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838216#3838216
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838216
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
