[jira] [Commented] (AMQ-6086) Broker stop and start are not at all thread safe - we can do better

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627527#comment-16627527 ] 

ASF subversion and git services commented on AMQ-6086:
------------------------------------------------------

Commit cae66f5d37943ede480330aa05e7b886ba089ff3 in activemq's branch refs/heads/master from gtully
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=cae66f5 ]

AMQ-6086 - variant with broker.schedulerSupport=true; same fix with additional test


> 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
>            Priority: Major
>             Fix For: 5.13.1, 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
(v7.6.3#76005)