Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <688254535.1247459495493.JavaMail.jira@brutus>
Date: Sun, 12 Jul 2009 21:31:35 -0700 (PDT)
From: "Ivan (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2069) Thread deadlock in
 ActiveMQEndpointWorker class
In-Reply-To: <1463339873.1232070899372.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Ivan updated AMQ-2069:
----------------------

    Attachment: AMQ-2069.patch

I tried to provide a patch for it, please help to review it.
Thanks !

> 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
>         Attachments: AMQ-2069.patch
>
>
> 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.