[JBoss JIRA] (WFLY-2228) EJB and web module cannot have the same name in an ear
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-2228?page=com.atlassian.jira.plugin.... ]
Jozef Hartinger updated WFLY-2228:
----------------------------------
Attachment: weld-translator.ear
Attached reproducer
> EJB and web module cannot have the same name in an ear
> ------------------------------------------------------
>
> Key: WFLY-2228
> URL: https://issues.jboss.org/browse/WFLY-2228
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.0.0.Beta1
> Reporter: Jozef Hartinger
> Assignee: Eduardo Martins
> Fix For: 8.0.0.CR1
>
> Attachments: weld-translator.ear
>
>
> Having an ear project like this:
> {code}
> weld.translator.ear
> +--weld-translator.war
> +--weld-translator.jar
> {code}
> I am no longer able to deploy it to WildFly. This is a regression caused by the following commit: https://github.com/wildfly/wildfly/commit/d4aecbe5d2b241befa5da43b19c2d07...
> The deployment exception:
> {noformat}
> 10:45:56,835 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta1 "WildFly" started in 3433ms - Started 180 of 217 services (62 services are lazy, passive or on-demand)
> 10:46:22,816 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /home/jharting/jboss/Weld/wildfly-8.0.0.Beta1/standalone/data/content/41/4cdfd11cd5283d5356778f396c618ca2477c6b/content
> 10:46:22,842 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "weld-translator.ear" (runtime-name: "weld-translator.ear")
> 10:46:22,912 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "weld-jsf-translator-war-2.1.0-SNAPSHOT.war")
> 10:46:22,912 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "null" (runtime-name: "weld-jsf-translator-ejb-2.1.0-SNAPSHOT.jar")
> 10:46:23,147 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016002: Processing weld deployment weld-translator.ear
> 10:46:23,192 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.0.1.Final
> 10:46:23,340 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment weld-jsf-translator-war-2.1.0-SNAPSHOT.war
> 10:46:23,353 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016002: Processing weld deployment weld-jsf-translator-ejb-2.1.0-SNAPSHOT.jar
> 10:46:23,366 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named TranslatorControllerBean in deployment unit subdeployment "weld-jsf-translator-ejb-2.1.0-SNAPSHOT.jar" of deployment "weld-translator.ear" are as follows:
> java:global/weld-translator/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:app/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:module/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:global/weld-translator/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/TranslatorControllerBean
> java:app/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/TranslatorControllerBean
> java:module/TranslatorControllerBean
> 10:46:23,369 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SentenceTranslator in deployment unit subdeployment "weld-jsf-translator-ejb-2.1.0-SNAPSHOT.jar" of deployment "weld-translator.ear" are as follows:
> java:global/weld-translator/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:app/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:module/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:global/weld-translator/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/SentenceTranslator
> java:app/weld-jsf-translator-ejb-2.1.0-SNAPSHOT/SentenceTranslator
> java:module/SentenceTranslator
> 10:46:23,392 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: weld-translator.ear
> 10:46:23,430 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.1.0 (2013-10-07 08:46)
> 10:46:23,448 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment weld-translator.ear
> 10:46:24,654 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-8) Initializing Mojarra 2.2.3-jbossorg-1 20130910-1739 for context '/weld-translator'
> 10:46:25,490 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS018210: Register web context: /weld-translator
> 10:46:25,569 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "weld-translator.ear" (runtime-name : "weld-translator.ear")
> 10:46:43,715 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS018224: Unregister web context: /weld-translator
> 10:46:43,731 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016009: Stopping weld service for deployment weld-translator.ear
> 10:46:43,775 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: weld-jsf-translator-ejb-2.1.0-SNAPSHOT.jar) in 65ms
> 10:46:43,777 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment null (runtime-name: weld-jsf-translator-war-2.1.0-SNAPSHOT.war) in 68ms
> 10:46:43,779 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment weld-translator.ear (runtime-name: weld-translator.ear) in 70ms
> 10:46:43,820 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/jharting/jboss/Weld/wildfly-8.0.0.Beta1/standalone/data/content/41/4cdfd11cd5283d5356778f396c618ca2477c6b/content
> 10:46:43,821 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "weld-translator.ear" (runtime-name: "weld-translator.ear")
> 10:47:10,201 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/jharting/jboss/Weld/wildfly-8.0.0.Beta1/standalone/data/content/d9/22ca6b33304b2cccc227cdf8f6aadeedad88f9/content
> 10:47:10,203 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "weld-translator.ear" (runtime-name: "weld-translator.ear")
> 10:47:10,223 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "null" (runtime-name: "weld-translator.jar")
> 10:47:10,223 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "weld-translator.war")
> 10:47:10,297 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment weld-translator.ear
> 10:47:10,310 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016002: Processing weld deployment weld-translator.war
> 10:47:10,311 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment weld-translator.jar
> 10:47:10,314 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named TranslatorControllerBean in deployment unit subdeployment "weld-translator.jar" of deployment "weld-translator.ear" are as follows:
> java:global/weld-translator/weld-translator.jar/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:app/weld-translator.jar/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:module/TranslatorControllerBean!org.jboss.weld.examples.translator.TranslatorController
> java:global/weld-translator/weld-translator.jar/TranslatorControllerBean
> java:app/weld-translator.jar/TranslatorControllerBean
> java:module/TranslatorControllerBean
> 10:47:10,314 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named SentenceTranslator in deployment unit subdeployment "weld-translator.jar" of deployment "weld-translator.ear" are as follows:
> java:global/weld-translator/weld-translator.jar/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:app/weld-translator.jar/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:module/SentenceTranslator!org.jboss.weld.examples.translator.Translator
> java:global/weld-translator/weld-translator.jar/SentenceTranslator
> java:app/weld-translator.jar/SentenceTranslator
> java:module/SentenceTranslator
> 10:47:10,318 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."weld-translator.ear"."weld-translator.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."weld-translator.ear"."weld-translator.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "weld-translator.jar" of deployment "weld-translator.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Beta1.jar:8.0.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.concurrent.ee.context.config.weld-translator.weld-translator is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2384) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2384) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.setupConcurrentContext(EEConcurrentContextProcessor.java:110)
> at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.processModuleDescription(EEConcurrentContextProcessor.java:71)
> at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.deploy(EEConcurrentContextProcessor.java:54)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Beta1.jar:8.0.0.Beta1]
> ... 5 more
> 10:47:10,329 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "weld-translator.ear")]) - failure description: {
> "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"weld-translator.jar\" of deployment \"weld-translator.ear\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.concurrent.ee.context.config.weld-translator.weld-translator is already registered"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"weld-translator.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"weld-translator.ear\".beanmanager]",
> "jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".batch is missing [jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".beanmanager]",
> "jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".beanmanager]"
> ]
> }
> 10:47:10,338 ERROR [org.jboss.as.server] (management-handler-thread - 3) JBAS015870: Deploy of deployment "weld-translator.ear" was rolled back with the following failure message:
> {
> "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"weld-translator.jar\" of deployment \"weld-translator.ear\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.concurrent.ee.context.config.weld-translator.weld-translator is already registered"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"weld-translator.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"weld-translator.ear\".beanmanager]",
> "jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".batch is missing [jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".beanmanager]",
> "jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"weld-translator.ear\".\"weld-translator.war\".beanmanager]"
> ]
> }
> 10:47:10,351 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: weld-translator.jar) in 18ms
> 10:47:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: weld-translator.war) in 21ms
> 10:47:10,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment weld-translator.ear (runtime-name: weld-translator.ear) in 23ms
> 10:47:10,358 INFO [org.jboss.as.controller] (management-handler-thread - 3) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."weld-translator.ear"."weld-translator.war".beanmanager (missing) dependents: [service jboss.deployment.subunit."weld-translator.ear"."weld-translator.war".weld.weldClassIntrospector, service jboss.deployment.subunit."weld-translator.ear"."weld-translator.war".batch]
> service jboss.deployment.unit."weld-translator.ear".beanmanager (missing) dependents: [service jboss.deployment.unit."weld-translator.ear".weld.weldClassIntrospector]
> service jboss.naming.context.java.module.weld-translator."weld-translator.war" (missing) dependents: [service jboss.deployment.subunit."weld-translator.ear"."weld-translator.war".INSTALL]
> JBAS014777: Services which failed to start: service jboss.deployment.subunit."weld-translator.ear"."weld-translator.jar".POST_MODULE
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (DROOLS-199) The entire kie build should work on maven 3.1.0 too
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer commented on DROOLS-199:
-----------------------------------------------
I run mvn clean install -Dfull with maven version 3.1.0; droolsjbpm-tools didn't copmpile:
https://gist.github.com/mbiarnes/6865529
> The entire kie build should work on maven 3.1.0 too
> ---------------------------------------------------
>
> Key: DROOLS-199
> URL: https://issues.jboss.org/browse/DROOLS-199
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> To reproduce:
> - Install maven 3.1.0
> - Run mvn-all.sh clean install -Dfull
> Note: Any changes to the pom must still allow them to run with 3.0.5 too.
> 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list.
> So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say).
> 2) There might be other surprises...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2217) Enable reload tests
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-2217?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski updated WFLY-2217:
-------------------------------------
Comment: was deleted
(was: A comment with security level 'JBoss Employee' was removed.)
> Enable reload tests
> -------------------
>
> Key: WFLY-2217
> URL: https://issues.jboss.org/browse/WFLY-2217
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Reporter: Bartosz Baranowski
> Assignee: Bartosz Baranowski
> Priority: Blocker
>
> Tests need not stay ignored any longer!
> Some tests which :reload are still ignored, even though :reload has been fixed ( well, it seems there is more to it due to other code changes )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2220) Unable to reload server after adding role and executing :reload
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-2220?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-2220:
--------------------------------
Parent: WFLY-490
Issue Type: Sub-task (was: Bug)
> Unable to reload server after adding role and executing :reload
> ---------------------------------------------------------------
>
> Key: WFLY-2220
> URL: https://issues.jboss.org/browse/WFLY-2220
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.CR1
>
>
> Start a clean build of WildFly 8 and execute the following commands in the CLI: -
> {code}
> [standalone@localhost:9990 /connect
> [standalone@localhost:9990 /] ./core-service=management/access=authorization/role-mapping=Operator:add
> {"outcome" => "success"}
> [standalone@localhost:9990 /] :reload
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /]
> {code}
> Results in the following error and the server shuts down: -
> {code}
> 15:15:02,275 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 15:15:02,278 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("access" => "authorization"),
> ("role-mapping" => "SuperUser")
> ]): java.lang.UnsupportedOperationException
> at java.util.Collections$UnmodifiableMap.put(Collections.java:1342) [rt.jar:1.7.0_17]
> at org.jboss.as.controller.access.management.WritableAuthorizerConfiguration.addRoleMappingImmediate(WritableAuthorizerConfiguration.java:163) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.domain.management.access.RoleMappingAdd$1.execute(RoleMappingAdd.java:76) [wildfly-domain-management-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:609) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:487) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:321) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:290) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:252) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> 15:15:02,287 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry]
> 15:15:02,290 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:15:02,297 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" stopped in 2ms
> {code}
> What is interesting is that the server is manually startable to something has gone wrong regarding resetting the runtime state of RBAC at the time of the reload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-1837) manual module testoutput is a bit disturbing NPE and dependencies missing
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-1837?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf updated WFLY-1837:
--------------------------------
Fix Version/s: (was: 8.0.0.CR1)
> manual module testoutput is a bit disturbing NPE and dependencies missing
> -------------------------------------------------------------------------
>
> Key: WFLY-1837
> URL: https://issues.jboss.org/browse/WFLY-1837
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha3
> Reporter: Bartosz Baranowski
> Assignee: JBoss SET
>
> Manual testmodule shows a lot of NPEs and dependency issues:
> {noformat}
> [org.jboss.as.ejb3] (EJB default - 2) JBAS014249: Error invoking method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname : java.lang.NullPointerException
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 13:06:07,613 ERROR [org.jboss.as.ejb3] (EJB default - 2) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname due to: java.io.IOException: Stream is closed
> at org.xnio.streams.BufferPipeOutputStream.closed(BufferPipeOutputStream.java:58) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.checkClosed(BufferPipeOutputStream.java:64) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:90) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
> at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:252)
> at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_25]
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler$1.write(AbstractMessageHandler.java:217)
> at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
> at org.jboss.marshalling.SimpleDataOutput.shallowFlush(SimpleDataOutput.java:328)
> at org.jboss.marshalling.river.RiverMarshaller.writeString(RiverMarshaller.java:1451)
> at org.jboss.marshalling.river.RiverMarshaller.writeNewSerializableClass(RiverMarshaller.java:1362)
> at org.jboss.marshalling.river.RiverMarshaller.writeSerializableClass(RiverMarshaller.java:1345)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:883)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> at org.jboss.marshalling.river.RiverObjectOutputStream.defaultWriteObject(RiverObjectOutputStream.java:159)
> at java.lang.Throwable.writeObject(Throwable.java:984) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:180)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:112)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: an exception which occurred:
> in field suppressedExceptions
> in object java.lang.NullPointerException@18e5c476
> {noformat}
> {noformat}
> 13:01:23,032 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("host" => "master"),
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): java.lang.NullPointerException
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.installHttpManagementServices(HttpManagementAddHandler.java:137) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.host.controller.operations.HttpManagementAddHandler.performRuntime(HttpManagementAddHandler.java:97) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT]
> {noformat}
> {noformat}
> 13:01:23,493 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014613: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "native-interface")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.remoting.authentication_provider.management is missing [jboss.server.path.\"jboss.server.temp.dir\"]",
> "jboss.remoting.endpoint.management.management.operation.handler is missing [jboss.as.server-controller]",
> "jboss.remoting.endpoint.management.channel.management is missing [jboss.remoting.endpoint.management.shutdown.executor]",
> "jboss.remoting.server.management is missing [jboss.binding.management-native, jboss.socket-binding-manager]"
> ]}
> 13:01:23,494 INFO [org.jboss.as.controller] (pool-2-thread-1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.as.server-controller (missing) dependents: [service jboss.remoting.endpoint.management.management.operation.handler]
> service jboss.binding.management-native (missing) dependents: [service jboss.remoting.server.management]
> service jboss.remoting.endpoint.management.shutdown.executor (missing) dependents: [service jboss.remoting.endpoint.management.channel.management]
> service jboss.server.path."jboss.server.temp.dir" (missing) dependents: [service jboss.remoting.authentication_provider.management]
> service jboss.socket-binding-manager (missing) dependents: [service jboss.remoting.server.management]
> 13:01:23,495 INFO [org.jboss.as.server] (pool-2-thread-1) JBAS015888: Creating http management service using socket-binding (management-http)
> 13:01:23,496 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.environment not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months