[AMQ-6693] SQLException when concurrently moving messages to DLQ

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.14.0
• Fix Version/s: 5.15.0
• Component/s: JDBC, Message Store
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 01/Jun/17 10:56
• Updated: 01/Jun/17 11:04
• Resolved: 01/Jun/17 11:04

Description

with the jdbc message store and the absence of a security context moving messages to the dlq on transaction rollback and exhausted redelivery is completed using the broker context.
However the long term connection associated with a jdbc context is not thread safe. It is typically associated with an incoming connection which is.
If multiple consumers poison ack concurrently the broker can step over itself using this shared context.
The long term connection context should be ignored for the broker.

Issue Links

• is part of: AMQ-5141 Message expiry that is done as part of a removeSubscription command should not use the clients credentials.