Bug 1054984

Summary: [GSS] (6.2.x) Initialization of MBeans uses wrong TCCL
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: Class LoadingAssignee: Kyle Lape <klape>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bmaxwell, cdewolf, jmartisk, klape, smumford
Target Milestone: CR2   
Target Release: EAP 6.2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP, it was found that an application's TCCL (thread context class loader) was not appropriately set when initializing MBeans found in .sar files. This meant that resources in the deployment were not available to the MBean upon initialization. In this update to the product, the TCCL is now set appropriately surrounding the call to the MBean initialization and MBeans can now access deployment resources upon initialization.
Story Points: ---
Clone Of: 1054972 Environment:
Last Closed: 2014-06-02 12:50:09 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: 1054972    
Bug Blocks: 1049365    

Description Kyle Lape 2014-01-17 21:31:24 UTC
** EAP 6.2.x backport

org.jboss.as.service.ParsedServiceDeploymentProcessor#newInstance should set the TCCL before creating the MBean instance.

Comment 2 Scott Mumford 2014-02-27 04:51:10 UTC
This bug has been marked for inclusion in the 6.2.2 Release Notes.

To meet PM request to have a draft of the document available for review by 4th March 2014, ECS needs a Cause, Consequence, Fix and Result to be supplied in the Doc Text field above.

Comment 3 Jan Martiska 2014-03-04 13:25:09 UTC
Verified in 6.2.2.CR2.