[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on LOGMGR-67:
-----------------------------------------------
Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 994744|https://bugzilla.redhat.com/show_bug.cgi?id=994744] from ON_QA to ASSIGNED
> Improve LogManager formatter capability: System resources, thread ID and minified category
> ------------------------------------------------------------------------------------------
>
> Key: LOGMGR-67
> URL: https://issues.jboss.org/browse/LOGMGR-67
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 1.3.2.Final
> Environment: JBoss EAP 6.0.1
> Reporter: Jeremy KUHN
> Assignee: James Perkins
> Labels: jboss
> Fix For: 1.5.0.Final, 2.0.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Hello,
> We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture.
> The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting.
> We are missing:
> - Thread ID (Thread names are too long and of different length that disturb the reading of logs)
> - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles.
> - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs.
> Regards
--
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
12 years, 9 months
[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on LOGMGR-67:
-----------------------------------------------
Ondrej Lukas <olukas(a)redhat.com> made a comment on [bug 994744|https://bugzilla.redhat.com/show_bug.cgi?id=994744]
Unfortunatelly verification failed. Thread ID and Minified log categories are ok, but setting system property works bad. If I add %${test.property} to formatter and start server with -Dtest.property=property that use "p" from word property as %p and then log of that part looks like INFOroperty.
> Improve LogManager formatter capability: System resources, thread ID and minified category
> ------------------------------------------------------------------------------------------
>
> Key: LOGMGR-67
> URL: https://issues.jboss.org/browse/LOGMGR-67
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 1.3.2.Final
> Environment: JBoss EAP 6.0.1
> Reporter: Jeremy KUHN
> Assignee: James Perkins
> Labels: jboss
> Fix For: 1.5.0.Final, 2.0.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Hello,
> We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture.
> The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting.
> We are missing:
> - Thread ID (Thread names are too long and of different length that disturb the reading of logs)
> - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles.
> - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs.
> Regards
--
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
12 years, 9 months
[JBoss JIRA] (WFLY-2228) EJB and web module cannot have the same name in an ear
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2228?page=com.atlassian.jira.plugin.... ]
Eduardo Martins resolved WFLY-2228.
-----------------------------------
Resolution: Duplicate Issue
Same as WFLY-2223 which already has a PR submitted
> 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
12 years, 9 months
[JBoss JIRA] (WFLY-2228) EJB and web module cannot have the same name in an ear
by Jozef Hartinger (JIRA)
Jozef Hartinger created WFLY-2228:
-------------------------------------
Summary: 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
12 years, 9 months
[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
12 years, 9 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
12 years, 9 months