[
https://issues.apache.org/jira/browse/QPID-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530816
]
Robert Greig commented on QPID-614:
-----------------------------------
Aidan, are you saying that the real issue has been masked by the exception
handler?
That makes sense since in this case the timings didn't imply a timeout.
What was the real exception for this issue?
> Race condition on queue browser close
> -------------------------------------
>
> Key: QPID-614
> URL: https://issues.apache.org/jira/browse/QPID-614
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Affects Versions: M2
> Environment: Any
> Reporter: Robert Greig
> Assignee: Robert Greig
> Attachments: QPID-614-blockingmethod-exception.patch,
> QueueBrowserFailure.txt
>
>
> Occasional systests failure due to (presumably) a deadlock when closing a
> queue browser:
> org.apache.qpid.client.JMSAMQException: Error closing consumer:
> org.apache.qpid.AMQTimeoutException: Server did not respond in a timely
> fashion [error code 408: Request Timeout]
> at
> org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:502)
> at
> org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:452)
> at
> org.apache.qpid.client.AMQQueueBrowser.close(AMQQueueBrowser.java:130)
> at
> org.apache.qpid.test.client.QueueBrowserTest.testQueueBrowserMsgsRemainOnQueue(QueueBrowserTest.java:128)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
