[GitHub] activemq-artemis pull request: Duplicate delivery over Bridge and ...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq-artemis pull request: Duplicate delivery over Bridge and ...

asfgit
GitHub user clebertsuconic opened a pull request:

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

    Duplicate delivery over Bridge and other failures

   

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

    $ git pull https://github.com/clebertsuconic/activemq-artemis master

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

    https://github.com/apache/activemq-artemis/pull/291.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 #291
   
----
commit 34b66351fbe0cc2f1f5106181c73cefbca94f53d
Author: Clebert Suconic <[hidden email]>
Date:   2015-12-29T05:30:37Z

    ignoring stuff from cmake / native build

commit 96849a42b756b3ba4f8ab65fff668893c59fc39f
Author: Clebert Suconic <[hidden email]>
Date:   2016-01-05T00:49:27Z

    ARTEMIS-332 - Duplicate delivery over Bridges under OME scenarios, paging and other failures
   
    https://issues.apache.org/jira/browse/ARTEMIS-332

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq-artemis pull request: Duplicate delivery over Bridge and ...

asfgit
Github user asfgit closed the pull request at:

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


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