Bug 1054972

Summary: [GSS] (6.3.0) Initialization of MBeans uses wrong TCCL
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: Class LoadingAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bmaxwell, jmartisk, kkhan, lcosti
Target Milestone: DR1   
Target Release: EAP 6.3.0   
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:
: 1054984 (view as bug list) Environment:
Last Closed: 2014-06-28 15:41:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1054984    

Description Kyle Lape 2014-01-17 21:14:06 UTC
org.jboss.as.service.ParsedServiceDeploymentProcessor#newInstance should set the TCCL before creating the MBean instance.

Comment 2 Jan Martiska 2014-03-04 12:52:36 UTC
Verified in 6.3.0.DR1.