[AMQ-4017] Demand Forwarding Bridge uses value of asyncDispatch for advisory consumers

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.1, 5.6.0
• Fix Version/s: 5.7.0
• Component/s: Broker
• Labels: advisory dispatch network networkConnector
• Assignee: Gary Tully
• Reporter: Raúl Kripalani
• Created: 04/Sep/12 15:41
• Updated: 05/Sep/12 09:24
• Resolved: 05/Sep/12 09:24

Description

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.

Issue Links

• is related to: AMQ-3985 ActiveMQConnection temp advisory consumer should use asyncDispatch - can cause deadlock with slow consumers