qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPIDJMS-139) Message flow to JMS synchronous consumer unexpected ceases
Date Tue, 17 Nov 2015 17:24:11 GMT

     [ https://issues.apache.org/jira/browse/QPIDJMS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Keith Wall updated QPIDJMS-139:
    Affects Version/s: 0.7.0

> Message flow to JMS synchronous consumer unexpected 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message