Bug 1054984 - [GSS] (6.2.x) Initialization of MBeans uses wrong TCCL
Summary: [GSS] (6.2.x) Initialization of MBeans uses wrong TCCL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Class Loading
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.2
Assignee: Kyle Lape
QA Contact:
URL:
Whiteboard:
Depends On: 1054972
Blocks: eap62-cp02-blockers
TreeView+ depends on / blocked
 
Reported: 2014-01-17 21:31 UTC by Kyle Lape
Modified: 2018-12-05 16:58 UTC (History)
5 users (show)

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.
Clone Of: 1054972
Environment:
Last Closed: 2014-06-02 12:50:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-822 0 Major Resolved MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL 2014-08-08 07:56:09 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.