[
https://issues.apache.org/jira/browse/QPIDJMS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058291#comment-15058291
]
Robbie Gemmell commented on QPIDJMS-139:
----------------------------------------
Added a test that uses the test peer to mimmicks the broker defect, which then
exposes the other issue in Proton, resulting in detection of the credit
mismatch on the wire. Also updated to proton-j 0.12.0-SNAPSHOT to get a fix
that makes proton, and in turn the client, able to handle the broker behaviour
more gracefully.
Will switch to proton 0.11.1 upon release.
> Message flow to JMS synchronous consumer unexpectedly ceases
> ------------------------------------------------------------
>
> Key: QPIDJMS-139
> URL: https://issues.apache.org/jira/browse/QPIDJMS-139
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Fix For: 0.7.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
