[
https://issues.apache.org/jira/browse/AMQ-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447760#comment-13447760
]
Raul Kripalani commented on AMQ-4017:
-------------------------------------
IRC chat record with gtully:
{quote}
17:14:06 raul: hey, quick question... what is the dispatchAsync on the network
connector used for? is it only used when listening for advisories?
17:24:05 gtully: raul: it is also used for local proxy consumers that will do
the forwarding... in fact, I don't think we should use that option for the
advisory consumer, it should always be async as a block would propagate back to
the broker
17:29:30 raul: gtully, I think it's being used for the advisory consumer at
least on 5.5.1: DemandForwardingSubscription.startRemoteBridge, inside the
'demandConsumerInfo' ConsumerInfo
17:30:35 gtully: raul: it is, think that is a bug waiting to happen if folks
use dispatchAsync=false
{quote}
> 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
> Labels: advisory, dispatch, network, networkConnector
>
> 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
