Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.15
-
None
Description
I've seen CombinedTest fail twice this evening with the following stack trace on java-bdb.0-9-1. I don't think I've ever seen the test fail before.
Whilst CombinedTest itself seems of questionable value, the Qpid client stack trace (java.lang.IllegalStateException: dispatcher is not started) seems potentially worrying as the client code (org.apache.qpid.test.unit.client.forwardall.Client) has called connection#start() so the dispatcher should be running.
CombinedTest testForwardAll Error Didn't receive all messages... got 0 expected 1 java.lang.Exception: Didn't receive all messages... got 0 expected 1 at org.apache.qpid.test.unit.client.forwardall.Client.waitUntilComplete(Client.java:116) at org.apache.qpid.test.unit.client.forwardall.Client.shutdownWhenComplete(Client.java:82) at org.apache.qpid.test.unit.client.forwardall.CombinedTest.testForwardAll(CombinedTest.java:58) at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:237) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:135)
Examining the logs I see:
IoReceiver - /127.0.0.1:59237 2012-01-25 22:44:25,298 INFO [qpid.message.subscription.close] [con:1,409(guest@/127.0.0.1:59237/test)/ch:1] [sub:1,178(vh(/test)/qu(ServiceQueue)] SUB-1002 : Close IoReceiver - /127.0.0.1:59237 2012-01-25 22:44:25,298 INFO [apache.qpid.server.AMQChannel] Requeuing 1 unacked messages. for [/127.0.0.1:59237(guest):1] Dispatcher-Channel-1 2012-01-25 22:44:25,298 ERROR [apache.qpid.thread.LoggingUncaughtExceptionHandler] Uncaught exception in thread "Dispatcher-Channel-1" java.lang.IllegalStateException: dispatcher is not started at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:3192) at org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:55) at org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:3349) at java.lang.Thread.run(Thread.java:680)