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-595) When creating JMS bridge management API should pass bridge name to JMS broker
Date Thu, 28 Jul 2016 14:20:21 GMT

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

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

GitHub user jbertram opened a pull request:

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

    ARTEMIS-595 additional JSON fixes

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/677.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 #677
    
----
commit aa0d7b6d013763c97b24896ef1164f7ad6271e66
Author: jbertram <jbertram@apache.org>
Date:   2016-07-27T20:07:39Z

    ARTEMIS-595 additional JSON fixes

----


> When creating JMS bridge management API should pass bridge name to JMS broker
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-595
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-595
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.3.0
>            Reporter: Chen Maoqian
>
> In situations where there are multiple JMS bridges being created it woudl help if bridge
name is logged in the server name. This helps with recognising which JMS bridge  is having
problems.
> For this to work the JBoss messaging API layer has to pass bridge name to the JMS broker.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message