Bug 1327502

Summary:	[GSS](6.4.z) HornetQ JMS Bridge should have bridge name in its logging.
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tom Ross <tom.ross>
Component:	JMS	Assignee:	Tom Ross <tom.ross>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.7	CC:	bmaxwell, fnasser, jmesnil, jtruhlar, pmackay, rnetuka
Target Milestone:	CR1
Target Release:	EAP 6.4.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 12:54:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1324262, 1325387

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.