activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name
Date Fri, 24 Jun 2016 21:57:16 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348753#comment-15348753
] 

ASF GitHub Bot commented on ARTEMIS-596:
----------------------------------------

GitHub user jbertram opened a pull request:

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

    ARTEMIS-596 fix JMS bridge example

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/601.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 #601
    
----
commit dbaf46376b1f550b3fa7bd52ccb0cc39215ff552
Author: jbertram <jbertram@apache.org>
Date:   2016-06-24T19:36:51Z

    ARTEMIS-596 fix JMS bridge example

----


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

Mime
View raw message