[
https://issues.apache.org/jira/browse/QPIDJMS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058278#comment-15058278
]
ASF subversion and git services commented on QPIDJMS-139:
---------------------------------------------------------
Commit e489ebad66e9ccb6053db5e1a4a8f0e9fa41f0ab in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e489eba ]
QPIDJMS-139: add test exercising underlying issue PROTON 1077 exposed by the
broker behaviour QPID 6947, update to proton 0.12.0-SNAPSHOT which includes
change to handle it better
> 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]
