[jbosstools-issues] [JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022299#comment-13022299 ] 

Rob Stryker commented on JBIDE-18366:
-------------------------------------

More information here, as an official response from rht:   https://access.redhat.com/solutions/312453

Seems I'll need to code this up in implementation. I'm not sure exactly what the eclipse debugger does to connect, but, it's possible it's connecting some agent in this fashion? If that's the case, then it makes sense why this bug is more easily replicatable in eclipse and not in standalone. 

See also:  https://bugzilla.redhat.com/show_bug.cgi?id=1037970

> Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18366
>                 URL: https://issues.jboss.org/browse/JBIDE-18366
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.CR1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log:
> {code}
> INFO: JBoss MSC version 1.1.5.Final-redhat-1
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start
> INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
> Sep 17, 2014 11:27: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:111)
>         at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611)
>         at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489)
>         at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290)
>         at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285)
>         at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132)
>         at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299)
>         at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292)
>         at org.jboss.as.server.ServerService.boot(ServerService.java:346)
>         at org.jboss.as.server.ServerService.boot(ServerService.java:321)
>         at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
>         at java.lang.Thread.run(Thread.java:695)
> 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:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
>         ... 11 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:106)
>         at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
>         at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
>         at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>         at java.lang.Thread.run(Thread.java:695)
>         at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot
> FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)