Page History

...

Investigation of QPID-1871 has highlighted a race condition between the Dispatcher and the clients request to rollback.

Problem Summary

The problem here is that the Dispatcher has the ability to hold on to a message so when the rollback
process is believed to have completed the Dispatcher then rejects the final message AFTER the TxRollback
so that one message gets sent ahead of the other messages. The reject is dropped as the message has been
resent. This is specific to the Java Client causing the Java Broker to return messages out of order. This may be the reason that the RollbackOrderTest has been disabled. It is not clear currently if this will also affect the CPP broker. Further investigation is in required.

...

1. Extract Dispatcher code to separate class and validate interface
2. Update AMQSession to use new Dispatcher interface.
3. Augment FlowControllingBlockingQueue to allow the injection of 'ServiceRequests'

Comment Responses