activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-6773) Calling external code while holding a lock sometimes results in deadlock
Date Mon, 18 Sep 2017 16:41:00 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-6773.
-----------------------------
    Resolution: Won't Fix

> Calling external code while holding a lock sometimes results in deadlock
> ------------------------------------------------------------------------
>
>                 Key: AMQ-6773
>                 URL: https://issues.apache.org/jira/browse/AMQ-6773
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Tim Bain
>
> A user reports that multiple different deadlocks have occurred when ActiveMQ is run in
the context of a Mule application, due to our invoking the ActiveMQMessageConsumer.onMessage()
method (which can eventually call external code) while holding a lock. http://activemq.2283324.n4.nabble.com/Fwd-Deadlock-caused-by-ActiveMQMessageConsumer-dispatch-due-to-onEvent-invocation-td4723587.html
has the details of what occurred, as he has described it.
> Since one of the prime rules for avoiding deadlocks is to avoid invoking external code
while holding locks, we should figure out how to invoke onMessage() at a time when we don't
hold the lock, while still protecting ourselves from whatever race conditions could occur
if we concurrently invoked more than one of the methods protected by the lock.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message