[
https://issues.apache.org/jira/browse/AMQ-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032784#comment-16032784
]
ASF subversion and git services commented on AMQ-6693:
------------------------------------------------------
Commit c50dc6ff00aa864f22cf7527e733a36567214f0b in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c50dc6f ]
[AMQ-6693] ignore the long term connection associated with the broker context,
fix and test
> 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)
