[
https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348425#comment-15348425
]
ASF GitHub Bot commented on ARTEMIS-596:
----------------------------------------
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 <tom.r...@redhat.com>
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.
----
> JMS Bridge logger message should be identified by the bridge name
> -----------------------------------------------------------------
>
> Key: ARTEMIS-596
> URL: https://issues.apache.org/jira/browse/ARTEMIS-596
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Tom Ross
> Fix For: 1.4.0
>
>
> In situations where there are many JMS bridges defined on a broker it would
> be very helpful if the bridge logger identified each message by the bridge
> name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
