[AMQ-3694] Blocked/Slow advisory consumers in duplex network connector, eventually breaks request/reply with temps

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Broker, Connector
• Labels: activemq blocking networkconnector requestreply temp
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 01/Feb/12 15:18
• Updated: 20/Jun/13 13:37
• Resolved: 01/Feb/12 16:18

Description

In duplex network connectors, the destinations and temp advisories are not acked. This leads to a buildup of advisory messages on the bridging broker and missing advisories on the target.
In the main, when the numbers of destinations is static and there are no temp queues per roundtrip this goes unnoticed.
If request/reply is used over a network with a temp queue per request (a bit of an anti pattern, they are typically per connection), the problem is quickly visible with the default prefetch. Very quickly advisories for temp queue creation and producer consumers get blocked and communication comes to a halt.
The root cause is that advisories are not acked in the duplex case so we can only get 750 (.75*prefetch) of them before we block.

symptom

javax.jms.JMSException: The destination temp-queue://ID:xxx-xxx-0:7:17 does not exist.

or replies do not get propagated back because the consumer advisory is blocked.