[ https://issues.apache.org/activemq/browse/AMQ-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38015 ]
Sridhar Komandur commented on AMQ-920: -------------------------------------- Rob/James, I have two-way communication working on my desktop with Discovery Network Connector between two brokers. I will monitor it for some time and send a patch to you next week for review. Thanks & have a great weekend. Regards - Sridhar Komandur > Two TCP connection requirement for bidirectional message flow ... > ----------------------------------------------------------------- > > Key: AMQ-920 > URL: https://issues.apache.org/activemq/browse/AMQ-920 > Project: ActiveMQ > Issue Type: Improvement > Components: Connector > Reporter: Sridhar Komandur > Assigned To: Rob Davies > > We noticed the following during our testing .... > When a broker A establishes connection to broker B, the message flow is > unidirectional from A to B. > This is a an issue for us: For example, consider brokers associated with > business critical services X and Y. There are many secondary services that > either monitor/feed off of the messages coming from them. > A FOO service would like to process messages going from X to Y. So in FOO's > broker configuration we add X's name. However, messages are not going to > flow from X to FOO, till X initiates a connection to FOO. It may not be > desirable/possible to change business critical brokers' configuration for > usage scenarios like this. > TCP is bidirectional and asymmetry at connection establishment should not be > translated to the higher level network connector. Is there a fundamental > need/justification for this design that I may not be aware of ? Otherwise I > would like to explore other design options. > Thanks > Regards > - Sridhar Komandur -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.