GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/117

    ARTEMIS-179

    I left each of these commits distinct so there would be a record of why 
each specific change was made since they had potentially far-reaching 
consequences.

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

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-179

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

    https://github.com/apache/activemq-artemis/pull/117.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 #117
    
----
commit f3be78a09633837d59ff1a79fa681b684bcd416c
Author: jbertram <[email protected]>
Date:   2015-08-05T17:17:21Z

    ARTEMIS-179 Expose disconnect/reconnect problem
    
    Currently a cluster bridge will continue to attempt to reconnect to
    a node that sends it a DISCONNECT until its reconnect-attempts is
    exhausted. A DISCONNECT message indicates that the node is not coming
    back so no reconnect attempt should be made and the bridge should be
    stopped, the bindings should be cleaned up, etc.
    
    The change to this test exposes this problem.

commit 682cad63f3e5c8d59be92602de32e523aae032ca
Author: jbertram <[email protected]>
Date:   2015-08-05T17:37:53Z

    ARTEMIS-179 Do not reconnect bridge on DISCONNECT
    
    Note: this breaks scale-down because the bindings are removed.

commit 3bb88c60ca683f5ff6788c0c5758a96210e346b5
Author: jbertram <[email protected]>
Date:   2015-08-06T21:28:56Z

    ARTEMIS-179 fix scale-down

commit 38188cdf2e6a1a04c6b900ec6bbc6bd49a406b4b
Author: jbertram <[email protected]>
Date:   2015-08-10T21:19:01Z

    ARTEMIS-179 fix BindingsClusterTest

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to