When duplicate message occur from network producer, message is stuck in DB even when enableAudit="false". The requirement is to use replaywhenNoConsumers=true so enabling the networkAudit feature is not an option to avoid this scenario is not feasible.Expectation: with enableAudit="false" and useCache=*false" would expect the duplicate message to be read from the DB and dispatched to the consumer - where the duplicate could be detected by consumer connection.In the attached unit test, it simulates a network duplicate message by stopping and restarting the consumerBroker after message (with message ID ending in 120) is persisted to consumerBrokerstore BUT BEFORE ack sent to the producerBroker over the network connection. When the network connection is reestablished the producerBroker resends message (with messageID ending in 120).All message are consumed as expected but we see the duplicate message remain in the DB| 2013-12-18 14:15:14,359 [main ] - DEBUG teMessagesTrappedJDBCStoreTest - ||ID||CONTAINER||MSGID_PROD||MSGID_SEQ||EXPIRATION||MSG||PRIORITY||XID|||