activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4017) Demand Forwarding Bridge uses value of asyncDispatch for advisory consumers
Date Wed, 05 Sep 2012 09:25:07 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-4017.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0
         Assignee: Gary Tully

fix in http://svn.apache.org/viewvc?rev=1381095&view=rev

the network connector advisory consumer is always asyncDispatch
the config flag only effects the local proxy consumers that forward
                
> Demand Forwarding Bridge uses value of asyncDispatch for advisory consumers
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-4017
>                 URL: https://issues.apache.org/jira/browse/AMQ-4017
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1, 5.6.0
>            Reporter: Raul Kripalani
>            Assignee: Gary Tully
>              Labels: advisory, dispatch, network, networkConnector
>             Fix For: 5.7.0
>
>
> The value of the dispatchAsync option on the networkConnector element is used when creating
the ConsumerInfo command that we dispatch to the remote broker with the aim of subscribing
to demand-related consumer advisories.
> A 'false' value means we risk blocking the remote broker if the local->remote broker
connection is blocked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message