You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/02/10 12:11:58 UTC
[jira] Resolved: (AMQ-3129) Can only have one duplex
networkConnection per transportConnection
[ https://issues.apache.org/jira/browse/AMQ-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3129.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.5.0
Regression: [Regression]
see http://svn.apache.org/viewvc?rev=1069339&view=rev rework of changes from AMQ-2774 that introduced the limitation
> Can only have one duplex networkConnection per transportConnection
> ------------------------------------------------------------------
>
> Key: AMQ-3129
> URL: https://issues.apache.org/jira/browse/AMQ-3129
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Adam Sussman
> Assignee: Gary Tully
> Fix For: 5.5.0
>
>
> AMQ-2774 introduced an unintended restriction on the number of duplex networkConnections you
> can make to the same port on a remote broker. This causes issues in scenarios where you want
> more than one duplex connection in order to have different settings for different kinds of destinations
> (for example: different conduitSubscription settings for topics vs queues).
> See:
> http://activemq.2283324.n4.nabble.com/conduit-subscriptions-vs-full-duplex-on-network-connections-td3208138.html
> and
> AMQ-2774
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira