| Summary: | Document use of ; char in Connection URLs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | gautric <gregoire> |
| Component: | Messaging_Programming_Reference | Assignee: | Joshua Wulf <jwulf> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Frantisek Reznicek <freznice> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | esammons, freznice, jskeoch, jwulf, lcarlon |
| Target Milestone: | 2.2.3 | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-19 04:27:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
gautric
2011-08-30 20:09:21 UTC
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/ |