[
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)
