With kahaDB as the default store some of the durable tests fail. The issue is the next message sequence gets out of sync when a durable sub is repeatedly drained such that an new message can be incorrectly seen as an ack. A consumer can miss a message as a result.
Tests that fail: org.apache.activemq.usecases.DurableConsumerCloseAndReconnectTest.testCreateDurableConsumerCloseThenReconnect
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Project Import||Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1m 30s||1||Gary Tully||01/Jun/10 18:28|