[
https://issues.apache.org/activemq/browse/AMQ-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48768#action_48768
]
gtully edited comment on AMQ-2069 at 1/16/09 3:54 AM:
----------------------------------------------------------
great. thanks for the heads up and
[contribution|http://activemq.apache.org/contributing.html]
Do you have a test case you could attach to this issue to protect your changes
into the future.
if you do a svn diff > amq-2059.diff and attach that with a license grant it
would be fantastic.
was (Author: gtully):
great. thanks for the heads up.
Do you have a test case you could attach to this issue to protect your changes
into the future.
if you do a svn diff > amq-2059.diff and attach that with a license grant it
would be fantastic.
> Thread deadlock in ActiveMQEndpointWorker class
> -----------------------------------------------
>
> Key: AMQ-2069
> URL: https://issues.apache.org/activemq/browse/AMQ-2069
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: Ivan
>
> It will happen when one thread is in a loop to try to connect the broker, in
> the meanwhile another thread calls the stop action.
> Thread A (in the run() method) holds the connectWork, and requires the
> shutdownMutex when it is notified by the notifyAll action by ThreadB.
> Thread B (in the stop() method) holds the shutdownMutex, and requires the
> connectWork in the disconnect method.
> I move the disconnect() invocation out of the synchronized (shutdownMutex)
> block, it works well.
> Thanks !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
