[
https://issues.apache.org/jira/browse/QPID-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner updated QPID-614:
-------------------------------
Attachment: QPID-614-blockingmethod-exception.patch
I thought's what was happening, but I was unable to reproduce it. It happens
reliably for me on the build machine now though, and debugging it further there
has revealed that while that could have been the cause it's not. What's
happening is that Object.wait is gettting a spurious wakup as documented here:
http://java.sun.com/javase/6/docs/api/java/lang/Object.html#wait(long) (hate
Java)
Here's a patch to make it use new 1.5 hotness like Lock and Condition.
> 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.
