On 10/06/2009 12:34 PM, Martin Ritchie wrote:
2009/10/6 Gordon Sim<[email protected]>:
I noticed the following hang in an automated build&test run. I believe it is
using the java broker(?). Almost everything appears to be idle, but the test
is blocked waiting for a latch.
Anyone else seeing this? Could this be a result of recent changes?
Sorry about that Gordon, when the test fails to receive all the
messages it becomes stuck. I fixed it this morning, r822170. I'd never
seen the test fail locally but our automated test boxes had also hung.
Strange thing is that the tests haven't failed since the fix went in.
If the same situation occured that caused the tests to hang
One thing I haven't figured out is why the new
AcknowledgeAfterFailoverTest when run against the CPP broker fails to
have the right number of messagse on the queue.
The test fails broker 1 then sends messages to, the now only active,
broker 2. When it then queries the broker for the
queue count it returns 0 rather than the messages just published. Any thoughts?
Are the brokers part of a cluster? Are there any consumers on the queue
in question?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
