activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <>
Subject [jira] Resolved: (AMQ-920) Two TCP connection requirement for bidirectional message flow ...
Date Sun, 29 Jul 2007 08:58:49 GMT


Rob Davies resolved AMQ-920.

       Resolution: Fixed
    Fix Version/s: 5.0.0

Fixed by SVN revision 560696

> Two TCP connection requirement for bidirectional message flow ...
> -----------------------------------------------------------------
>                 Key: AMQ-920
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Connector
>            Reporter: Sridhar Komandur
>            Assignee: Rob Davies
>             Fix For: 5.0.0
> 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.

View raw message