[AMQ-2540] Duplicate suppression lack of recovery with JDBCStore can result in "hung" queue afer failover of outstanding send or transaction.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3.0
• Fix Version/s: 5.3.1, 5.4.0
• Component/s: Message Store
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 18/Dec/09 13:00
• Updated: 21/Dec/09 12:50
• Resolved: 21/Dec/09 12:50

Description

during failover, when a commit or send reply is lost, such that the broker has completed the operation but the client does not see the reply, the operation and context will be replayed. This results in duplicate messages that should be suppressed. The AMQ reference store does this correctly but the audit check in the JDBCMessageStore does not do recovery so it is unaware of past events.
Adding some replay capability to the audit resolves this as it can then suppress duplicated.
The audit depth should limit the replay depth.

<jdbcPersistenceAdapter dataSource="#...." maxProducersToAudit="10000"/>

Issue Links

• depends upon: AMQ-2473 Async error occurred: java.lang.NullPointerException