7 Replies Latest reply on Mar 5, 2015 9:35 AM by andreas_w

Problem with weld in WildFly 8.2

andreas_w Dec 22, 2014 4:40 AM

Hi!

We are currently on the way to migrate our application to WildFly. We are able to deploy the application on WildFly 8.1 but not on WildFly 8.2. It seems that something is not working regarding to weld. We are getting the following Exception:

INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: <application>.ear
INFO  [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.2.6 (Final)
INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment <application>.ear
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."<application>.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."<application>.ear".WeldStartService: Failed to start service
  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.deployment.subunit."<application>.ear"."<application>ejb3.jar".component.<EJB>.VIEW."<package>.<EJB>".REMOTE not found
  at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
  at org.jboss.as.weld.services.bootstrap.WeldEjbInjectionServices.getComponentView(WeldEjbInjectionServices.java:149)
  at org.jboss.as.weld.services.bootstrap.WeldEjbInjectionServices.handleServiceLookup(WeldEjbInjectionServices.java:124)
  at org.jboss.as.weld.services.bootstrap.WeldEjbInjectionServices.registerEjbInjectionPoint(WeldEjbInjectionServices.java:106)
  at org.jboss.weld.injection.ResourceInjectionFactory$EjbResourceInjectionProcessor.getResourceReferenceFactory(ResourceInjectionFactory.java:243)
  at org.jboss.weld.injection.ResourceInjectionFactory$EjbResourceInjectionProcessor.getResourceReferenceFactory(ResourceInjectionFactory.java:238)
  at org.jboss.weld.injection.ResourceInjectionFactory$ResourceInjectionProcessor.createFieldResourceInjection(ResourceInjectionFactory.java:207)
  at org.jboss.weld.injection.ResourceInjectionFactory$ResourceInjectionProcessor.createResourceInjections(ResourceInjectionFactory.java:182)
  at org.jboss.weld.injection.ResourceInjectionFactory.discoverType(ResourceInjectionFactory.java:405)
  at org.jboss.weld.injection.ResourceInjectionFactory.getResourceInjections(ResourceInjectionFactory.java:92)
  at org.jboss.weld.injection.producer.ResourceInjector.<init>(ResourceInjector.java:59)
  at org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
  at org.jboss.weld.injection.producer.BeanInjectionTarget.<init>(BeanInjectionTarget.java:62)
  at org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:46)
  at org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
  at org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
  at org.jboss.weld.bean.ManagedBean.<init>(ManagedBean.java:91)
  at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:71)
  at org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:264)
  at org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
  at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
  at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
  at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
  at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
  at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
  ... 3 more

The strange thing is that if we turn off weld through comment the "subsystem" in the standalone.xml we can deploy our application on WildFly 8.2. It is also possible to turn weld on after first deployment. But if we upload a new ear file, we have the same problem again. Any ideas or we are doing something wrong?

Thanks in advance

1. Re: Problem with weld in WildFly 8.2

jaikiran Dec 31, 2014 11:32 PM (in response to andreas_w)

Do you have an application you can attach to this thread, that reproduces this?
Actions
2. Re: Problem with weld in WildFly 8.2

andreas_w Jan 10, 2015 7:16 AM (in response to jaikiran)

No, sorry. But for the moment we will use WildFly 8.1.
Actions
3. Re: Problem with weld in WildFly 8.2

nickarls Jan 11, 2015 12:36 PM (in response to andreas_w)

First thing that comes to mind is the the weld versions are different and there has been some tightening of the rules, a structure dump of the ear recursively would probably be helpful
Actions
4. Re: Problem with weld in WildFly 8.2

andreas_w Feb 25, 2015 9:23 AM (in response to nickarls)

We had time to analyze this in more detail. It seems that when it is not working weld is scanning our managedbeans from a war-file before the ejbs from a jar file. And then throwing an exception like I mentioned in my first post. Can we control somehow which jar, war file should be scanned first?
We deploy an ear file which includes some jar-file with ejbs and several war-files. Furthermore we are already using this "initialize-in-order" in the application.xml to ensure that the ejb.jar is deployed first.

Any ideas?
Actions
5. Re: Problem with weld in WildFly 8.2

andreas_w Mar 4, 2015 1:49 AM (in response to andreas_w)

No one has any idea? Or at least a hint for me what I could try.

thanks in advance
Actions
6. Re: Problem with weld in WildFly 8.2

jharting Mar 5, 2015 2:36 AM (in response to andreas_w)

This definitely looks like a Weld / WildFly integration bug. Any chance you could try to isolate the problem into a minimal application for us to reproduce?
Actions
7. Re: Problem with weld in WildFly 8.2

andreas_w Mar 5, 2015 9:35 AM (in response to jharting)

Thanks for your answer.
I can try, but this could take some time. In the meantime I posted it in the weld-forum too because I thought it is more a weld-problem than a problem in WildFly. See Problem with weld during deployment on WildFly 8.2
Actions

Go to original post