[
https://issues.jboss.org/browse/WFLY-6655?page=com.atlassian.jira.plugin....
]
Tom Ross commented on WFLY-6655:
--------------------------------
Hi Chen,
No, this is not enough. There two places where changes are needed. One is Artemis code and
the other is Wildly code.
This JIRA is for the wildly code change i.e. in JMSBridgeAdd class. Another is in artemis
itself, but it's more extensie than just adding name to constructor. I'll submit
PR today for all the changes.
When creating JMS bridge management API should pass bridge name to
JMS broker
-----------------------------------------------------------------------------
Key: WFLY-6655
URL:
https://issues.jboss.org/browse/WFLY-6655
Project: WildFly
Issue Type: Bug
Components: JMS
Environment: JBoss EAP 7.0
Reporter: Tom Ross
Assignee: 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.4.11#64026)