Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1054972 - [GSS] (6.3.0) Initialization of MBeans uses wrong TCCL
[GSS] (6.3.0) Initialization of MBeans uses wrong TCCL
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Class Loading (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity unspecified
: DR1
: EAP 6.3.0
Assigned To: David M. Lloyd
:
Depends On:
Blocks: 1054984
  Show dependency treegraph
 
Reported: 2014-01-17 16:14 EST by Kyle Lape
Modified: 2014-06-28 11:41 EDT (History)
4 users (show)

See Also:
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 11:41:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFLY-822 Major Resolved MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL 2016-08-16 03:20 EDT

  None (edit)
Description Kyle Lape 2014-01-17 16:14:06 EST
org.jboss.as.service.ParsedServiceDeploymentProcessor#newInstance should set the TCCL before creating the MBean instance.
Comment 2 Jan Martiska 2014-03-04 07:52:36 EST
Verified in 6.3.0.DR1.

Note You need to log in before you can comment on or make changes to this bug.