activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From catull <...@git.apache.org>
Subject [GitHub] activemq pull request #228: [AMQ-6601] AMQ with master and slave broker, shu...
Date Sat, 04 Mar 2017 20:06:34 GMT
GitHub user catull opened a pull request:

    https://github.com/apache/activemq/pull/228

    [AMQ-6601] AMQ with master and slave broker, shutting down slave causes a dead-lock

    This PR addresses the issue https://issues.apache.org/jira/browse/AMQ-6601.
    
    The proposed solution is to start the broker asynchronously, but only wait for its starting
up if it is the master (i.e. non-slave).
    
    Closes / fixes issue #6601.
    
    Credit goes to @lichtin for coming up with the solution.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/catull/activemq fix-issue-6601-shutdown-slave-broker

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/228.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #228
    
----
commit 5de4f788d17f406c713d42a1bd77c15b973ac0de
Author: Carlo Dapor <catull@gmail.com>
Date:   2017-03-04T20:01:34Z

    [AMQ-6601] AMQ with master and slave broker, shutting down slave causes dead-lock.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message