Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3E34918FD2 for ; Mon, 14 Dec 2015 19:09:49 +0000 (UTC) Received: (qmail 72577 invoked by uid 500); 14 Dec 2015 19:09:47 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 72481 invoked by uid 500); 14 Dec 2015 19:09:47 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 72040 invoked by uid 99); 14 Dec 2015 19:09:47 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2015 19:09:47 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 213092C1F87 for ; Mon, 14 Dec 2015 19:09:47 +0000 (UTC) Date: Mon, 14 Dec 2015 19:09:47 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056493#comment-15056493 ] ASF subversion and git services commented on AMQ-6086: ------------------------------------------------------ Commit fc4120e85016e094eee6d7a758c73f49f3db191b in activemq's branch refs/heads/activemq-5.13.x from [~gtully] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=fc4120e ] https://issues.apache.org/jira/browse/AMQ-6086 - test cannot validate all start failures scenarios at this time, suffice that start and stop complete ok (cherry picked from commit b7787bf6fbbb33b5d16b34dab07de52b76044a4c) > 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 > Assignee: 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)