[jboss-jira] [JBoss JIRA] (WFLY-1992) Invalid deployment in WildFly 8 - Errai, Weld, TicketMonster
Ricardo Garcia (JIRA)
jira-events at lists.jboss.org
Sun Sep 22 14:58:03 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806290#comment-12806290 ]
Ricardo Garcia edited comment on WFLY-1992 at 9/22/13 2:56 PM:
---------------------------------------------------------------
I got the same (or a very similar) problem when trying to install JBoss BRMS on wildfly-8.0.0.Alpha4. So, exactly, how do I fix (or work around) this error?
Also, I checked the Wildfly 8 and this is where weld is installed:
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\as\jsf-injection\main\weld-core-jsf-2.0.3.Final.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\api\main\weld-api-2.0.SP1.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\core\main\weld-core-impl-2.0.3.Final.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\spi\main\weld-spi-2.0.SP1.jar
So it appears that my Wildfly build already has Weld 2.0.3, so I'm confused now. Is this the same issue, a similar issue, or something completely different? Should I report it on weld, or open another ticket here?
(Or is it a BRMS problem?)
I'm attaching the log.
{code:text}
13:37:16,320 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jboss-brms.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-brms.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]
Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] public class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation cannot be a non-static inner class
at org.jboss.weld.injection.producer.BasicInjectionTarget.checkType(BasicInjectionTarget.java:81)
at org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjectionTarget.java:69)
at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:48)
at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:44)
at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129)
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]
... 3 more
{code}
was (Author: rick_777):
I got the same (or a very similar) problem when trying to install JBoss BRMS on wildfly-8.0.0.Alpha4. So, exactly, how do I fix (or work around) this error?
Also, I checked the Wildfly 8 and this is where weld is installed:
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\as\jsf-injection\main\weld-core-jsf-2.0.3.Final.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\api\main\weld-api-2.0.SP1.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\core\main\weld-core-impl-2.0.3.Final.jar
C:\wildfly-8.0.0.Alpha4\modules\system\layers\base\org\jboss\weld\spi\main\weld-spi-2.0.SP1.jar
So it appears that my Wildfly build already has Weld 2.0.3, so I'm confused now. Is this the same issue, a similar issue, or something completely different? Should I report it on weld, or open another ticket here?
(Or is it a BRMS problem?)
I'm attaching the log.
(P.S. how do I format for logs?)
-------------
13:37:16,320 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jboss-brms.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-brms.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]
Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] public class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation cannot be a non-static inner class
at org.jboss.weld.injection.producer.BasicInjectionTarget.checkType(BasicInjectionTarget.java:81)
at org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjectionTarget.java:69)
at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:48)
at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:44)
at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129)
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]
... 3 more
> Invalid deployment in WildFly 8 - Errai, Weld, TicketMonster
> ------------------------------------------------------------
>
> Key: WFLY-1992
> URL: https://issues.jboss.org/browse/WFLY-1992
> Project: WildFly
> Issue Type: Bug
> Reporter: Emmanuel Bernard
>
> I am deploying TicketMonster which includes Errai and receives a deployment error that is not happening in JBoss AS 7.x nor EAP 6.x.
> Note that it could be
> - a WildFly error per se
> - a Weld error or change
> - an Errai error
> I am opening the issue here to track the problem down to its cause.
> {code}
> 15:00:17,818 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-5) starting errai cdi ...
> 15:00:18,731 INFO [org.jboss.errai.reflections.Reflections] (Thread-106) Reflections took 346 ms to scan 7 urls, producing 387 keys and 1384 values [using 2 cores]
> 15:00:18,815 WARN [org.jboss.weld.Bean] (MSC service thread 1-5) WELD-001529 An InjectionTarget is created for a class org.jboss.errai.bus.server.service.ErraiServiceImpl which does not have any appropriate constructor.
> 15:00:18,828 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (pool-20-thread-1) all services registered successfully
> 15:00:18,928 WARN [org.jboss.weld.Bootstrap] (weld-worker-2) WELD-001473 javax.enterprise.inject.spi.Bean implementation org.jboss.errai.cdi.server.ErraiServiceBean at 7adf1c57 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface.
> 15:00:18,928 WARN [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-001473 javax.enterprise.inject.spi.Bean implementation org.jboss.errai.cdi.server.MessageBusBean at 19b6b8f5 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface.
> 15:00:18,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."ticket-monster.war".component."org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."ticket-monster.war".component."org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1".WeldInstantiator: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [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_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] class org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1 cannot be a non-static inner class
> at org.jboss.weld.injection.producer.BasicInjectionTarget.checkType(BasicInjectionTarget.java:81)
> at org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjectionTarget.java:69)
> at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:48)
> at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:44)
> at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129)
> 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]
> ... 3 more
> 15:00:18,975 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "ticket-monster.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ticket-monster.war\".component.\"org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ticket-monster.war\".component.\"org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1\".WeldInstantiator: Failed to start service
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] class org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1 cannot be a non-static inner class"}}
> 15:00:18,977 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "ticket-monster.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ticket-monster.war\".component.\"org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ticket-monster.war\".component.\"org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1\".WeldInstantiator: Failed to start service
> Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple bean [EnhancedAnnotatedTypeImpl] class org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1 cannot be a non-static inner class"}}
> 15:00:18,986 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 73) JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service 'ticket-monster.war#primary'
> 15:00:18,987 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 73) HHH000227: Running hbm2ddl schema export
> 15:00:19,004 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 73) HHH000230: Schema export complete
> 15:00:19,007 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment ticket-monster.war
> 15:00:19,021 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 73) JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service 'ticket-monster.war#primary'
> 15:00:19,022 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010409: Unbound data source [java:jboss/datasources/ticket-monsterDS]
> 15:00:19,050 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment ticket-monster.war (runtime-name: ticket-monster.war) in 72ms
> 15:00:19,052 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."ticket-monster.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."ticket-monster.war".deploymentCompleteService, service jboss.undertow.deployment.default-host./ticket-monster]
> JBAS014776: Newly corrected services:
> service jboss.deployment.unit."ticket-monster.war".ee.ComponentRegistry (no longer required)
> JBAS014777: Services which failed to start: service jboss.deployment.unit."ticket-monster.war".component."org.jboss.errai.bus.server.servlet.StandardAsyncServlet$1".WeldInstantiator
> {code}
--
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
More information about the jboss-jira
mailing list