Description of problem: Inside "3.2.2. Connection URLs" section there is no information about char separator for 'brokerlist' option gsim talk about ";" char Version-Release number of selected component (if applicable): 2.0 JMS and JCA API How reproducible: n/a Steps to Reproduce: n/a Actual results: n/a Expected results: more details like brokerlist='<transport>://<host>[:<port>](;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' brokerlist='tcp://ip1:5672;tcp://ip2:5672;tcp://ip3:5672?ssl='true'&ssl_cert_alias='cert1'' Additional info:
Incorporated in Topic 7014
http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#sect-Failover_behavior_in_clients Text: brokerlist can take a semi-colon-separated list of brokers, like so: brokerlist='<transport>://<host>[:<port>](;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' For example: brokerlist='tcp://ip1:5672;tcp://ip2:5672;tcp://ip3:5672?ssl='true'&ssl_cert_alias='cert1'
Change incorporated and ok. -> VERIFIED
Taking second look I found trouble. generic pattern brokerlist='<transport>://<host>[:<port>](;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' is wrong as user may assume that broker parameters are relevant to all brokers, which is incorrect. Each broker in the list (separated by ';') can have separate broker options like this: amqp://guest:guest@/test?failover='roundrobin?cyclecount='2'' &brokerlist='tcp://ip1:5672?retries='5'&connectdelay='2000';tcp://ip2:5672?retries='5'&connectdelay='2000'' Please update generic pattern and add there above example to demonstrate more complex usage. See details and examples here: qpid.apache.org/books/0.18/Programming-In-Apache-Qpid/html/QpidJNDI.html -> ASSIGNED
Updated. Please check. http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Programming_Reference/index.html#Failover_behaviour_in_Java_JMS_Clients
I'm wondering whether to allow this change as the brokerlist generic patter is still the same == wrong: brokerlist='<transport>://<host>[:<port>](;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' The paragraph understands well that parameters are defined per broker 'Note that the broker option parameters are per-broker. ...' but I think it would be better if you change generic brokerlist pattern to be correct probably less readable. I'm proposing change of brokerlist generic pattern from: brokerlist='<transport>://<host>[:<port>](;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' to: brokerlist='<transport>://<host>[:<port>](?<param>=<value>)?(&<param>=<value>)*(;<transport>://<host>[:<port>])?(?<param>=<value>)?(&<param>=<value>)*' Let me know your view on this change, I'm eventually fine with comment 5 state if you provide good reason against proposed brokerlist change. -> ASSIGNED
No, you are right. I've updated the generic pattern to reflect that. http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/Messaging_Programming_Reference/index.html#Failover_behaviour_in_Java_JMS_Clients
I'm happy with the changes now. Thanks for cooperation. -> VERIFIED
MRG Messaging 2.2.3 docs have been released as of 14 November 2012, the docs are now available on https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_MRG/