[QPIDJMS-139] Message flow to synchronous consumer from Qpid Java broker unexpectedly ceases

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0
• Component/s: qpid-jms-client
• Assignee: Robbie Gemmell
• Reporter: Keith Wall
• Created: 17/Nov/15 17:22
• Updated: 06/Jan/16 12:32
• Resolved: 18/Dec/15 15:35

Description

Testing the Qpid JMS Client together with the Java Broker + Perftest framework reveals a problem. Message flow to one or more consumers sometimes ceases unexpectedly.

In the failure case, the Java Broker reports that the consumer has been is suspended (SUB-1003 messages) for an extended period, even though there are messages remaining on the queue. Investigation of a heap dump reveals that the last flow frame to be received from the client:

• deliveryCount value which matched the deliveries sent by the Broker.
• linkCredit zero
• drain true.

The Broker thus believes no more credit remains and suspends the consumer.

0.6.0 is affected. 0.7.0-SNAPSHOT is too. Rolling back to client 0.5.0 resolves the problem, as does setting jms.receiveLocalOnly in the connection url with 0.6.0 or the 0.7.0 SNAPSHOT.

There are more details on regard the reproduction on QPID-6863. Problem would not manifest with debug logging turned on.

Issue Links

• depends upon: PROTON-1077 receiver link and transport view of credit can become disjoint when sending link sends flow frames
• depends upon: QPIDJMS-145 update proton-j dependency to 0.11.1
• is related to: QPID-6947 [Java Broker] deliverycount advanced outside a previous drain attempt that used all credit
• is related to: QPID-6863 AMQP 1.0 message flow to consumers stops