[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... ]
Tim Fox commented on JBMESSAGING-1121:
--------------------------------------
Actually I think GUIDs are the only option, since different bridged servers also need
unique ids and they won't be in the same JGroups group so a shared sequence won't
work.
For JBM 2.0 using a GUID becomes a non issue since each node will have its own store.
I can do an experiment and see if there is much impact in making node_id a (potentially
long) string...
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