Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 11 Dec 2015 16:18:10 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12921092.1449850661000.336813.1449850690983@Atlassian.JIRA>
In-Reply-To: <JIRA.12921092.1449850661000@Atlassian.JIRA>
References: <JIRA.12921092.1449850661000@Atlassian.JIRA>
 <JIRA.12921092.1449850661642@arcas>
Subject: [jira] [Created] (AMQ-6086) Broker stop and start are not at all
 thread safe - we can do better
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gary Tully created AMQ-6086:
-------------------------------

             Summary: Broker stop and start are not at all thread safe - we can do better
                 Key: AMQ-6086
                 URL: https://issues.apache.org/jira/browse/AMQ-6086
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.13.0
            Reporter: Gary Tully
             Fix For: 5.14.0


If one thread starts a broker and a second tries to stop we can get in a mess. Particularly if there is blocking or locking in the mix. In some cases we are ok but there is no determinism.
In a simple case, the stop can complete before the start gets going at all and we miss the stop, leaving a dangling broker.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)