[
https://issues.apache.org/jira/browse/AMQ-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kestutis Gedminas updated AMQ-7154:
-----------------------------------
Description:
We get a deadlock on AMQ. After analysis, it looks like in case if expired
messages thread is processing DLQ queue at the same moment when poisonAck is
received we run into preexisting racing condition in code due to inconsistent
lock acquiring order.
[ !amq.svg|width=800!|^amq.svg]
[^threaddump.zip]
[^amq.svg]
was:
We get a deadlock on AMQ. After analysis, it looks like in case if expired
messages thread is processing DLQ queue at the same moment when poisonAck is
received we run into preexisting racing condition in code due to inconsistent
lock acquiring order.
!amq.svg|width=800!
[^threaddump.zip]
[^amq.svg]
> Broker Deadlock while processing expired DLQ messages
> -----------------------------------------------------
>
> Key: AMQ-7154
> URL: https://issues.apache.org/jira/browse/AMQ-7154
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.12.0
> Reporter: Kestutis Gedminas
> Priority: Major
> Attachments: amq.svg, threaddump.zip
>
>
> We get a deadlock on AMQ. After analysis, it looks like in case if expired
> messages thread is processing DLQ queue at the same moment when poisonAck is
> received we run into preexisting racing condition in code due to inconsistent
> lock acquiring order.
> [ !amq.svg|width=800!|^amq.svg]
>
> [^threaddump.zip]
> [^amq.svg]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
