Bug 969530 - ClassCastException when JBoss LogManager is initialized before the logging subsystem expects
Summary: ClassCastException when JBoss LogManager is initialized before the logging su...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.1.1
Assignee: James Perkins
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-31 17:39 UTC by Kyle Lape
Modified: 2018-12-09 17:02 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If the JBoss LogManager was added to the boot classpath, for example for custom Java agents (e.g. Introscope or JMX agent), the JBoss LogManager would be bootstrapped using the default configurator, rather than using the logging subsystem's own configurator. As the logging subsystem assumed that its own configurator would be used, this resulted in the JBoss EAP 6 failing to start, displaying the following error: ---- ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "logging"), ("console-handler" => "CONSOLE") ]): java.lang.ClassCastException: org.jboss.logmanager.PropertyConfigurator cannot be cast to org.jboss.as.logging.logmanager.ConfigurationPersistence ... ---- This issue has been fixed in this release of JBoss EAP 6, so that the the logging subsystem no longer assumes that its own configurator is used. If the logging subsystem's own configurator is not used, it replaces the original configurator (usually the default configurator). As a result of this fix, custom Java agents can now be used without affecting how the JBoss LogManager is initially configured.
Clone Of:
Environment:
Last Closed: 2013-09-16 20:27:19 UTC
Type: Bug


Attachments (Terms of Use)
Diff to configure jboss to fail (1.30 KB, patch)
2013-05-31 17:39 UTC, Kyle Lape
no flags Details | Diff


Links
System ID Priority Status Summary Last Updated
JBoss Issue Tracker WFLY-1432 Major Closed ClassCastException when JBoss LogManager is initialized before the logging subsystem expects 2018-02-20 21:32:13 UTC

Description Kyle Lape 2013-05-31 17:39:25 UTC
Created attachment 755327 [details]
Diff to configure jboss to fail

09:28:18,984 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014612: Operation ("add") failed - address: ([
    ("subsystem" => "logging"),
    ("console-handler" => "CONSOLE")
]): java.lang.ClassCastException: org.jboss.logmanager.PropertyConfigurator cannot be cast to org.jboss.as.logging.logmanager.ConfigurationPersistence
        at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:93)
        at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:81)
        at org.jboss.as.logging.LoggingOperations$LoggingOperationStepHandler.execute(LoggingOperations.java:154)
        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
        at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45]
        at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45]
        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]

Comment 1 JBoss JIRA Server 2013-06-03 16:41:46 UTC
James Perkins <jperkins@redhat.com> made a comment on jira WFLY-1432

Pull request merged

Comment 3 Petr Kremensky 2013-06-19 12:56:26 UTC
Verified on EAP 6.1.0 ER1

Comment 4 Petr Kremensky 2013-06-19 12:57:46 UTC
Sorry, I meant 6.1.1 ER1


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