Bug 1327502 - [GSS](6.4.z) HornetQ JMS Bridge should have bridge name in its logging.
Summary: [GSS](6.4.z) HornetQ JMS Bridge should have bridge name in its logging.
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 1325387
TreeView+ depends on / blocked
 
Reported: 2016-04-15 09:13 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:54:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1521 0 Major Resolved HornetQ JMS Bridge should bridge name in its logging. 2017-06-22 14:19:42 UTC
Red Hat Knowledge Base (Article) 2259991 0 None None None 2016-07-11 07:22:27 UTC

Description Tom Ross 2016-04-15 09:13:14 UTC 
HornetQ JMS Bridge does not contain bridge name in its logging. When multiple bridge are used it is difficult to guess which bridge is reporting an error. 
The logging should contain bridge name.
Comment 2 JBoss JIRA Server 2016-05-27 06:51:20 UTC 
Tom Ross <toross> updated the status of jira HORNETQ-1521 to Resolved
Comment 4 Peter Mackay 2016-06-28 13:48:40 UTC 
Verified with EAP 6.4.9.CP.CR2
Comment 5 Petr Penicka 2017-01-17 12:54:48 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 6 Petr Penicka 2017-01-17 12:57:15 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.