Hi,

here is the stacktrace

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

But "<EJB>" is always different. Regarding which class is produced first. The strange thing is, that sometimes it is working. But just in vary rare cases.

Hi,

thanks for the answer. I can't show the exact source code, sorry. But the ejb's are looking like this:

@Stateless
@Local(SomeClassLocal.class)
@Remote(SomeClass.class)
public class SomeClassBean implements SomeClassLocal, SomeClass {


     public String getValue(){
          return "test"
     }

}

ManagedBean in application.war

public class MyManagedBean {

     public void getDataFromEjb(){
          
          InitialContext ictx = new InitialContext();
          SomeClass ejbObj = (SomeClass)ictx.lookup(jndiURL);
          ejbOjb.getValue()

     }
}

I hope this helps a bit. What I forget to mention. The application was running first on an application server which only supports JavaEE 5. Therefore we haven't used any CDI. But if we tried to disable weld completly some of our masks loaded completly slow. If you need more information just let me know. And thanks again for taking a look at our problem.

oh, yes beside the ManagedBeans we are having some servlets which are using @EJB annotations. They are living either in the application.war or in another war-file which is included in the ear-file.

And with "<EJB>" I mean it is always another class where the problem occurs. I guess depending on how the classes are processed. So "<EJB>" is just a placeholder for example for SomeClassBean (which I mentioned in my previous post).

Thanks for your answer and your help.

It happens a lot of times for us. I would say from 10 deployments it isn't working 8 times. But the strange thing is, that it seems to work when it was deployed once. So if we don't change our app and starting wildfly a few times it seems to work. But after we deploy a new version we are getting the same error.

It seems that the resolving of an @EJB injection point sometimes happen before the ejb jar is really processed (ejb service registered). 

This makes sense for me, but is there anything we can do against it?

okay, thanks.

The strange thing is that with WildFly 8.1 we haven't had this problems. I can try to create an application which I can send to you but this will take some time. Would it help you if I would provide more log-messages? Like setting the log-level for weld to "trace"?

okay, the application is a bit difficult, because I can't send you our application. You said you tried it with an own application? Could you give me access to it and I try to modify it in a way that it looks more like our application. Or is this not possible? I will try to set the log-level to debug and post the results here afterwards.

And thanks for your help.

Thank you. I will try this. But I have to install maven first. ;-)

I will let you know about the results.