[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18366:
-------------------------------------
I doubt this can be fixed for final without clear steps to replicate.
> 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.0.Final
>
>
> 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.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-18523:
-----------------------------------
Summary: [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
Key: JBIDE-18523
URL: https://issues.jboss.org/browse/JBIDE-18523
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.0.CR2
When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18523:
--------------------------------
Fix Version/s: 4.1.2.Final
(was: 4.2.0.CR2)
> [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18523
> URL: https://issues.jboss.org/browse/JBIDE-18523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.2.Final
>
>
> When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18312) CordovaSim struggles with POST
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18312?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-18312:
-------------------------------------
< I did try it many times and was not able to enter any digit. Text field has focus but is not accepting any character
Is it coupled with *all* fields or only date?
> CordovaSim struggles with POST
> ------------------------------
>
> Key: JBIDE-18312
> URL: https://issues.jboss.org/browse/JBIDE-18312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: hybrid1001.zip, post_error.png
>
>
> I will attach the project.
> The $.ajax post does not fire correctly from inside of CordovaSim - but it does via the iOS Simulator and from a real Android Device. Nothing in the error message on the client-side.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18436) Central archetype versions should depend on selected runtime version
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-18436.
------------------------------
Different Java EE Web Project was created for EAP 6.3, EAP 6.1 and no runtime. Closing.
> Central archetype versions should depend on selected runtime version
> --------------------------------------------------------------------
>
> Key: JBIDE-18436
> URL: https://issues.jboss.org/browse/JBIDE-18436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8 CR1, Fedora 20
> Reporter: Vineet Reynolds
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> A newly created project using the "Java EE Web Project" in JBoss Central, uses the {{org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4}} and {{org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-4}} BOMs in the {{dependencyManagement}} section.
> These are the older versions. It should instead be using the BOMs from the {{org.jboss.bom.wfk}} and {{org.jboss.bom.eap}} groupIds instead.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months