[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow command line configuration of ServerPeerID

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384424 ] 
            
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