FSW ER6 fails to start in roughly one of 20 attempts. The error message is printed WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager Dec 04, 2013 8:30:38 AM org.jboss.msc.service.ServiceContainerImpl <clinit> INFO: JBoss MSC version 1.0.4.GA-redhat-1 Dec 04, 2013 8:30:39 AM org.jboss.as.server.ApplicationServerService start INFO: JBAS015899: JBoss Red Hat JBoss Fuse Service Works 6.0.0.ER6-redhat-1 (AS 7.2.0.Final-redhat-8) starting Dec 04, 2013 8:30:40 AM org.switchyard.as7.extension.SwitchYardExtension initialize INFO: SwitchYard version 1.1.0.M3-redhat-2 Dec 04, 2013 8:30:40 AM org.jboss.as.controller.AbstractOperationContext executeStep ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:232) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225) at org.jboss.as.server.ServerService.boot(ServerService.java:333) at org.jboss.as.server.ServerService.boot(ServerService.java:308) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) at java.lang.Thread.run(Thread.java:724) Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) at java.util.concurrent.FutureTask.get(FutureTask.java:111) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) ... 10 more Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) at org.jboss.threads.JBossThread.run(JBossThread.java:122) Dec 04, 2013 8:30:41 AM org.jboss.as.server.ServerService boot FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. The same behaviour was observed also by jsedlace and pdrozd. The issue is present on different Linux distros and both for Oracle and OpenJDK. The issue is typically more frequent (but not exclusive to) when FSW is started from JBDS.
Just to confirm - this issue is not limited to initial (after an install) start - but is seen when a server is restarted, yes?
Is this issue still present with ER8? If so can we have log files showing the problem? Also can you provide specific information about the environment, i.e. OS versions, JDK versions, hardware?
It is still present in ER8. There are no log files as you can see from the exception - it fails to initiate logging - only the message is printed to console. We all are using Lenovo T5xx machines, a mix of Linux distros - Fedora, RHEL and Ubuntu, using OpennJDK 7. Regarding the way how to reproduce the issue. Really the easisest way is to install JBDS, configre ER8 to run from it and then start the server in Debug mode. If the server startup sequence is ok, then terminate it and repeat. Using this method roughly 1 from 5 starts the issue is present.
A console dump from ER8 start WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager Jan 10, 2014 8:30:56 AM org.jboss.msc.service.ServiceContainerImpl <clinit> INFO: JBoss MSC version 1.0.4.GA-redhat-1 Jan 10, 2014 8:30:56 AM org.jboss.as.server.ApplicationServerService start INFO: JBAS015899: JBoss Red Hat JBoss Fuse Service Works 6.0.0.ER8-redhat-1 (AS 7.2.1.Final-redhat-10) starting Jan 10, 2014 8:30:57 AM org.switchyard.as7.extension.SwitchYardExtension initialize INFO: SwitchYard version 1.1.1-p2-redhat-2 Jan 10, 2014 8:30:57 AM org.jboss.as.controller.AbstractOperationContext executeStep ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:232) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225) at org.jboss.as.server.ServerService.boot(ServerService.java:333) at org.jboss.as.server.ServerService.boot(ServerService.java:308) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) at java.lang.Thread.run(Thread.java:724) Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) at java.util.concurrent.FutureTask.get(FutureTask.java:111) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) ... 10 more Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) at org.jboss.threads.JBossThread.run(JBossThread.java:122) Jan 10, 2014 8:30:57 AM org.jboss.as.server.ServerService boot FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
This is an EAP issue and occurs long before any of the server components have been initialised. There is a race condition in the startup code whereby the LogManager can be initialised to the java.util.logging.LogManager rather than the org.jboss.logmanager.LogManager.
We have tried to execute this scenario with EAP 6.1.1 and EAP 6.2.0 server (clean EAP server without any extensions) and we have not seen this issue. Tested with OpenJDK 1.6 and OpenJDK 1.7.
It's a race condition, not guaranteed to occur
Kevin will take a look at EAP 6.3 to see if this is resolved or not. There is no EAP bug associated with it.
Just an fyi that this happens to me at intervals as well. Unpredictable as to exactly when but it seems to happen more frequently when I stop EAP at work and start it up at home or going the other way. jboss-fsw-installer-6.0.0.GA-redhat-4.jar jboss-eap-6.1
(In reply to Doug Toppin from comment #11) > Just an fyi that this happens to me at intervals as well. Unpredictable as > to exactly when but it seems to happen more frequently when I stop EAP at > work and start it up at home or going the other way. > > jboss-fsw-installer-6.0.0.GA-redhat-4.jar > jboss-eap-6.1 java version "1.7.0_60" Java(TM) SE Runtime Environment (build 1.7.0_60-b19) Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
I've spoken with Jimmy (GSS/EAP) about this. They would welcome a bug against EAP if we have evidence to suggest it's an underlying EAP problem that's causing this. Relevant: EAP 6.3.2 (next Rollup) should ship in November. Another possibility might be EAP 6.4, due in February/March.
*** Bug 1133067 has been marked as a duplicate of this bug. ***
this occurs for me fairly regularly. it happens when starting FSW (6.0) from JBDS (7.1.1.GA). jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar jboss-fsw-installer-6.0.0.GA-redhat-4.jar java version "1.7.0_55" Java(TM) SE Runtime Environment (build 1.7.0_55-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode) win 7 enterprise sp1. I have dell e6440 with 8gb ram and a 5400 hdd (slow). My "fix" is to just push start again when FSW fails to start. For me, this happens about every other time I start fsw. this also happens on my home pc with a similar software stack.
I have been unable to reproduce this on the latest EAP 6.3.1 distribution and the latest Java 1.7 distribution from Oracle even after running countless restarts. @Mark Lybarger, could you provide the standard output if you start JBoss with this property: -Djava.util.logging.manager=invalid.classname That property is only used when a failure is imminent, and we believe setting it to an invalid classname or even literally "invalid.classname" will cause an exception to be logged to the standard out location for your JBoss EAP instance. That exception should help us better understand what is leading to the failure because it will show where it originated, and we would like it if you could capture the stdout and attach it to this bugzilla. Currently, we think there are a handful of unique situations that make this happen, and we are trying track down all of them that we can.
I thought this was resolved after applying FSW roll up patch 2 yesterday to resolve a different issue. But I saw this error again this afternoon... Here's the output you requested: Could not load Logmanager "invalid.classname" java.lang.ClassNotFoundException: invalid.classname at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at java.util.logging.LogManager$1.run(LogManager.java:191) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.<clinit>(LogManager.java:181) at java.util.logging.Logger.demandLogger(Logger.java:339) at java.util.logging.Logger.getLogger(Logger.java:393) at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:55) at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:823) at sun.management.Agent.startLocalManagementAgent(Agent.java:144) at sun.management.Agent.startAgent(Agent.java:264) at sun.management.Agent.agentmain(Agent.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:384) at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:407) WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager Oct 30, 2014 3:04:07 PM org.jboss.msc.service.ServiceContainerImpl <clinit> INFO: JBoss MSC version 1.0.4.GA-redhat-1 Oct 30, 2014 3:04:07 PM org.jboss.as.server.ApplicationServerService start INFO: JBAS015899: JBoss Red Hat JBoss Fuse Service Works 6.0.0.GA-redhat-2 (AS 7.2.1.Final-redhat-10) starting Oct 30, 2014 3:04:08 PM org.switchyard.as7.extension.SwitchYardExtension initialize INFO: SwitchYard version 1.1.1-p7-redhat-1 Oct 30, 2014 3:04:08 PM org.jboss.as.controller.AbstractOperationContext executeStep ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:232) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225) at org.jboss.as.server.ServerService.boot(ServerService.java:333) at org.jboss.as.server.ServerService.boot(ServerService.java:308) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) at java.lang.Thread.run(Thread.java:745) Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:188) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) ... 10 more Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103) at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:122) Oct 30, 2014 3:04:08 PM org.jboss.as.server.ServerService boot FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
@Mark It looks like you've configured your JVM to use the Sun JMX server: at sun.management.Agent.startLocalManagementAgent(Agent.java:144) The use of the Sun JMX server is known to cause this issue and is actually not a supported use case in EAP. JMX clients should be using the remoting-jmx protocol provided by JBoss to connect to EAP servers. If you still want to try to make JBoss work with the use of the Sun JMX agent, I suggest reading this KB doc: https://access.redhat.com/solutions/312453
It is not difficult to find users replicating this issue. Most replicating users are users of JBDS. You'll note the FSW users here in this bugzilla are also using JBDS, as are most public-forum users experiencing this bug. http://stackoverflow.com/questions/21134303/logmanager-exception-in-jboss-as-7-1-with-java-util-logger I'm not very knowledgeable about the internal details of eclipse's remote debugger, but it's possible it's connecting some agent which causes this bug. I'll be looking into making JBDS use the workaround solutions referenced here: https://access.redhat.com/solutions/312453
@Rob There is an explanation for your comment #33 (same explanation for #29). In these cases they are executing an agent (premain-class). Theses means it's a piece of java code executed before jboss-modules main class and they are using the same class loader. The sequence of events are: 1) premain-class is loaded and it references to LogManager 2) The class loader instantiates the LogManager class (javaagent is going to share the same system class loader). 3) In this case, because the constant -Djava.util.logging.manager is not set to the right LogManager, it instantiates the jdk logmanager. This happens before the logic of the jboss-modules [1] 4) When the main is executed and the logging instantiation happens, the jboss modules fails to setup the right the LogManager. At this points jboss-modules triggers a warning. 5) Logging extension is loaded and it fails because it does not allow to have a different LogManager installed [2]. I don't think this setup is supported; the logic in jboss-modules [1] is quite specific about the LogManager. In any case, I don't have an explanation for the description of this BZ (non deterministic behaviour); it must be something like this. Maybe, for some reason, sometimes the instantiation of the LogManager by the java agent is delayed giving the oportunity to jboss-modules to setup the LogManager properly. (this could cause the race condition). [1] https://github.com/jboss-modules/jboss-modules/blob/1.4.3.Final/src/main/java/org/jboss/modules/Main.java#L467 [2] https://github.com/wildfly/wildfly-core/blob/2.0.0.Alpha4/logging/src/main/java/org/jboss/as/logging/LoggingExtension.java#L143
I can easily reproduce this without resorting to any of the techniques described above (at least, I don't think I'm doing any of those things). All I have to do is have JVisualVM running (and attached to nothing) before I try to start the app. Some specifics of my environment: Eclipse Mars Wildfly 8.2.1 final JBoss AS Tools 3.0.3 Final Oracle JDK 1.8.0_25 Win 7/64 hope this info is helpful for someone.
A customer just reported the same issue while running BRMS Suite installer on top of EAP 6.4.4. See below the Bootstrap Environment used by our BxMS installer: JBoss Bootstrap Environment JBOSS_HOME: "C:\jboss-eap-6.4" JAVA: "C:\Program Files\Java\jdk1.7.0_75\bin\java" JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.policy-permissions=true -Djboss.modules.system.pkgs=org.jboss.byteman". Full installer log attached ....... They are not able to use our installer with this issue happening.
Created attachment 1120915 [details] BRMS Installer Log