[ https://issues.apache.org/jira/browse/AMQ-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-6693. ----------------------------- Resolution: Fixed > SQLException when concurrently moving messages to DLQ > ----------------------------------------------------- > > Key: AMQ-6693 > URL: https://issues.apache.org/jira/browse/AMQ-6693 > Project: ActiveMQ > Issue Type: Bug > Components: JDBC, Message Store > Affects Versions: 5.14.0 > Reporter: Gary Tully > Assignee: Gary Tully > Fix For: 5.15.0 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)