Bug 1327510 - [GSS] (6.4.z) When creating JMS bridge management API should pass bridge name to HornetQ
Summary: [GSS] (6.4.z) When creating JMS bridge management API should pass bridge name...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.9
Assignee: Tom Ross
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap649-payload
TreeView+ depends on / blocked
 
Reported: 2016-04-15 09:32 UTC by Tom Ross
Modified: 2019-10-10 11:53 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:53:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 2259991 0 None None None 2016-06-29 09:44:36 UTC

Description Tom Ross 2016-04-15 09:32:52 UTC 
At the moment HornetQ does not log JMS bridge name when logging bridge errors. The scan very confusing when multiple bridges are used.
In order for HornetQ to log bridge name with each error JBoss management API should pass bridge name to HornetQ.
Comment 3 Peter Mackay 2016-06-28 13:49:44 UTC 
Verified with EAP 6.4.9.CP.CR2
Comment 4 Petr Penicka 2017-01-17 12:53:40 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.