[
https://issues.apache.org/jira/browse/QPIDJMS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056370#comment-15056370
]
Robbie Gemmell commented on QPIDJMS-139:
----------------------------------------
This appears to be happening due to unexpected behaviour by the broker
(advancing the delivery count outside of a drain attempt, QPID-6937), leading
to an issue in proton-j that Proton based peers wouldnt tend to expose (causing
link and transport state getting out of sync, PROTON-1077) that then lead to
the client thinking it has remaining credit when it doesn't.
> 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, 0.7.0
> Reporter: Keith Wall
>
> 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]
