[jira] [Closed] (QPID-7774) [JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover

["Lorenz Quack (JIRA)" <ji...@apache.org>]

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

Lorenz Quack closed QPID-7774.
------------------------------

> [JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7774
>                 URL: https://issues.apache.org/jira/browse/QPID-7774
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.22, 0.32, qpid-java-6.0.6, qpid-java-6.1.2
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>             Fix For: qpid-java-client-0-x-6.3.0, qpid-java-6.1.3
>
>         Attachments: 0001-QPID-7774-Improve-locking-when-using-failover-latch.patch
>
>
> If the client fails over when AMQP 0-8..0-91 is in use and the application is using a synchronous message receiver calling #receiveNoWait(), the application will always receive null.  The defect is longstanding.  It goes back at least until 0.22.  Other synchronous receive calls and asynchronous message listeners are unaffected.  The 0-10 path is unaffected too.
> The problem is {{org.apache.qpid.client.AMQConnection#isFailingOver}} and org.apache.qpid.client.AMQProtocolHandler#startFailoverThread.   The former assumes that the failover latch will be nullified after a successful failover but {{startFailoverThread}} does not organise for this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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