2:18 p.m.
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
2:23 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1121:
----------------------------------------------
If you configure it as:
<attribute name="ServerPeerID">${server.peer.id}</attribute>
and then define "server.peer.id" system property with -Dserver.peer.id=77 (or
whatever) , it works.
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
2:33 p.m.
New subject: [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:
-----------------------------------------------
Right; this JIRA is a request to have the official property name defined and that system
property substitution syntax added in the standard file that's integrated into the
AS.
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
1:03 p.m.
New subject: [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
1:54 p.m.
New subject: [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:
--------------------------------------
We may be able to do away with the necessity of the user configuring a unique id by doing
something like the following:
When a server starts look in it's config files for the server id, if it does not exist
request one from a sequence managed by the co-ordinator. Once it obtains an id, write it
into its config files
When the server starts the next time it will already have the generated id so it will know
which queues in the database "belong" to it.
Server ids need to be persistent since each node owns it's own set of queues.
Alternatively we could generate the ids as GUIDs then we avoid a global sequence, but then
lookups in the DB based on a GUID string will be slower than an int, potentially hitting
JBM performance.
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
1:56 p.m.
New subject: [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
2:11 p.m.
New subject: [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:
-----------------------------------------------
That would be useful information. But, TBH, the integer approach you have now could be
fine, if you regard trusting the user to pass in the correct value at startup to be
adequate persistence (seems OK to me.) I used to dislike your use of integer, but now
it's growing on me; i.e. it makes a perfectly good jvmRoute for the web tier. A GUID
would be a pretty long to append to web session ids.
Suggest we try and use the
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 thread to have a
general discussion of where node ids might be needed and what format is required for each
use case. That thread's got Scott's attention. If we can come up with a single
approach that meets all needs, that would be ideal.
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
2:26 p.m.
New subject: [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:
-----------------------------------------------
LOL. This all seemed so familiar. Then I found
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108609 .
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
7:23 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Tim Fox updated JBMESSAGING-1121:
---------------------------------
Fix Version/s: JBM Stable branch
(was: AS 5.0 Integration)
(was: EAP/SOA-P Integration)
Priority: Minor (was: Major)
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
Priority: Minor
Fix For: JBM Stable branch
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
4:25 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Tim Fox reassigned JBMESSAGING-1121:
------------------------------------
Assignee: Clebert Suconic (was: Tim Fox)
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: Clebert Suconic
Priority: Minor
Fix For: Stable branch
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
3:19 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Clebert Suconic closed JBMESSAGING-1121.
----------------------------------------
Resolution: Done
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: Clebert Suconic
Priority: Minor
Fix For: Stable branch
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
3:21 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Clebert Suconic closed JBMESSAGING-1121.
----------------------------------------
Resolution: Done
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: Clebert Suconic
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
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
3:21 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Clebert Suconic reopened JBMESSAGING-1121:
------------------------------------------
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: Clebert Suconic
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
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
3:21 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=all ]
Clebert Suconic updated JBMESSAGING-1121:
-----------------------------------------
Fix Version/s: 1.4.0.SP3.CP02
1.4.1.beta2
(was: Stable branch)
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: Clebert Suconic
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
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
6151
days inactive
6289
days old
13 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Clebert Suconic (JIRA)
-
Ovidiu Feodorov (JIRA)
-
Tim Fox (JIRA)