[GitHub] activemq-artemis pull request #599: ARTEMIS-596 JMS Bridge messages should b...

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

[GitHub] activemq-artemis pull request #599: ARTEMIS-596 JMS Bridge messages should b...

asfgit
GitHub user TomRoss opened a pull request:

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

    ARTEMIS-596 JMS Bridge messages should be identified.

    In cases where there are many JMS bridges defined on a broker it should
    be possible to identify any error message by a bridge name.

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

    $ git pull https://github.com/TomRoss/activemq-artemis jms-bridge-name

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

    https://github.com/apache/activemq-artemis/pull/599.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 #599
   
----
commit 5bca681c1aaef32e52f51472c03cb1d5ac77b999
Author: Tom Ross <[hidden email]>
Date:   2016-06-24T13:38:05Z

    ARTEMIS-596 JMS Bridge messages should be identified.
   
    In cases where there are many JMS bridges defined on a broker it should
    be possible to identify any error message by a bridge name.

----


---
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 #599: ARTEMIS-596 JMS Bridge messages should b...

asfgit
Github user asfgit closed the pull request at:

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


---
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.
---