[QPID-1917] the java async profile is failing due to suspicous broker behavior when async store is loaded

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6
• Fix Version/s: 0.5
• Component/s: C++ Broker
• Assignee: Kim van der Riet
• Reporter: Rafael H. Schloming
• Created: 18/Jun/09 15:48
• Updated: 29/Jul/13 18:53
• Resolved: 24/Jul/09 11:36

Description

The async profile fails when running against the cpp broker with persistence enabled. I've analyzed the cause, and it appears that MessageListenerMultiConsumerTest.testAsynchronousRecieve is running successfully, however the messages that it sends and then consumes are erroneously recovered the next time the broker restarts, and this causes failures in many subsequent tests.

I've included the log output from the test run. I've modified MessageListenerMultiConsumerTest to generate a random UUID to identify each test run, and marked each message with this test-id. This makes it clear that the messages which were consumed according to the logs here:

TEST-org.apache.qpid.client.MessageListenerMultiConsumerTest.testAsynchronousRecieve.out

Are actually resent in the test that follows here:

TEST-org.apache.qpid.client.MessageListenerMultiConsumerTest.testRecieveInterleaved.out

The broker logging in the first file indicates that the broker did receive the acknowledgment for the messages in question, and the second file shows those messages being sent anyways. Note that there is a broker restart in between the two tests.

Issue Links

• is blocked by: QPID-3079 message.accept command should be completed on a per-dequeue basis