[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_1... ]
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------
The name of the property probably becomes a discussion whose scope extends across the AS,
since if there's a requirement to provide an id to each server, we might as well use
that value elsewhere. See
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 .
Also, there should be a cmd line switch to set this. Gone are the days of telling people
in trainings, etc "fire up 2 AS instances with run - c all and you'll have a
cluster." Saying "run -i 0 - c all" and "run -i 1 -c all" is
fairly palatable. Saying "run -Dserver.peer.id=0 -c all" and "run
-Dserver.peer.id=1 - c all" .... well, yuck.
Allow command line configuration of ServerPeerID
------------------------------------------------
Key: JBMESSAGING-1121
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Clustering
Affects Versions: 1.4.0.GA
Reporter: Brian Stansberry
Assigned To: Tim Fox
Fix For: AS 5.0 Integration, EAP 4.3 Integration
The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you
want to set up a cluster, the only way to get it to work is to manually change the value
in that file in each node. This needs to be configurable from the command line; i.e via
system property substitution.
Need to be sure any changes made in the messaging-service.xml are also reflected in
docs/examples/binding-manager/sample-bindings.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira