[ https://issues.apache.org/jira/browse/AMQ-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056232#comment-15056232 ]
ASF subversion and git services commented on AMQ-6086: ------------------------------------------------------ Commit 455a628305dc49476d7033701901d119db3fffdb in activemq's branch refs/heads/master from [~gtully] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=455a628 ] https://issues.apache.org/jira/browse/AMQ-6086 - avoid logging npe on attempted start of persistence adapter post stop > 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)