[
https://issues.apache.org/jira/browse/AMQ-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3641.
-----------------------------
Resolution: Not A Problem
This is working as designed. If you can show a test case where this is causing
some issue please reopen and attach it here.
> ActiveMQMessageConsumer dispatches messages while holding mutex
> ---------------------------------------------------------------
>
> Key: AMQ-3641
> URL: https://issues.apache.org/jira/browse/AMQ-3641
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.5.1
> Environment: CentOS 5, Sun Java 1.6 64-bit, server mode
> Reporter: Tin Tvrtković
> Labels: concurrency, deadlock, mutex
>
> I'm using async message dispatch.
> I've noticed the ActiveMQMessageConsumer class dispatches messages to its
> listeners while holding a mutex (method name: dispatch(MessageDispatch md),
> mutex name unconsumedMessages). This mutex needs to be grabbed in other
> situations as well (like closing the connection), which can lead to
> deadlocks. Is this really the best way of handling this?
> I realize I can get around this problem in a number of ways, but this issue
> seems to be pretty deep in the client infrastructure, especially if another
> JMS framework is being used (like Spring JMS).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
