Bug 1327510

Summary:	[GSS] (6.4.z) When creating JMS bridge management API should pass bridge name to HornetQ
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, jmesnil, jtruhlar, msochure, 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:53:40 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1324262

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.