Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1613494

Summary:	[GSS](6.4.z) Wrong classLoader used in hornetq RA Reconnect
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Clebert Suconic <csuconic>
Component:	HornetQ	Assignee:	jboss-set
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	bmaxwell, csuconic, dcihak, msvehla, rstancel
Target Milestone:	CR1
Target Release:	EAP 6.4.21
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:45:42 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:	1567790, 1610346, 1610355

Description Clebert Suconic 2018-08-07 16:54:51 UTC

Description of problem:
The re-activation on hornetq, is using the wrong classLoader.

This is because a new Thread is started instead of using the WorkManager from the ResourceAdapter.

Version-Release number of selected component (if applicable):


How reproducible:

You could visually verify the classLoader used. This had issues in production for a customer after failover, and we couldn't replicate the exact classNotFoundException they had but we could assert the wrong classLoader i used. 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: