NPE in org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection

[claudio4j]

Hi, I am using EAP 6.1.1 (the subscription will be active only on Mar/30) and it throws the following error

16:31:42,961 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.subunit."grpfor-ear.ear"."grpfor.war".component."java.lang.Object".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.subunit."grpfor-ear.ear"."grpfor.war".component."java.lang.Object".WeldInstantiator: Failed to start service
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.NullPointerException
        at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:144)
        at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:154)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
        ... 3 more

Debug shows me the screen at http://i.imgur.com/0YHa4eP.png

The code is

            //look for field injection points
            Set<AnnotatedField<?>> _annFields = type.getFields();
            for (AnnotatedField<?> field : _annFields) {

I added the _annFields, just to put the type.getFields into a local attribute.

The type.getFields() returns null.

Do you see some condition this can result in null ?

The screenshot shows bean = null and componentClass = java.lang.Object

Thanks

Claudio

[luan.cestari]

It seems to be a bug (but I didn't find no records in jira now, so it should be a new one). I think you also noticed that the call http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-weld/7.2.0.Final/org/jboss/as/weld/injection/WeldE… made the NPE as the returned Set from type.getFields() must be null. As the 'type' comes from the loadClass call  ( http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-weld/7.2.0.Final/org/jboss/as/weld/injection/WeldE… ) and as that for doesn't do any validation for null collections, I would suspect that something during the  loadClass call ( http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.weld/weld-core/1.1.10.Final/org/jboss/weld/resources/ClassTran… ) might be with an issue.

What I think that might help, as the stack trace tell us that the previous call was http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… so, with log level set for debug we can see if we get this message http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… . I would also recommend to use Byteman to print the parameters and local variables before the NPE  ( http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… ) (e.g. Class<?> componentClass, Bean<?> bean, final BeanManagerImpl beanManager and AnnotatedType<?> type ). With those information we could know which exactly class and component arise the problem and how to reproduce it.

Kindest regards,

Luan

[luan.cestari]

I didn't saw the picture, so could you debug and see the values of the those parameters and variables so we could have a better clue what's going on behind the scenes? Also, I would say to try other EAP versions, but I'm sure you already tested with the latest one with patches.

[claudio4j]

This is an .ear project, where we used a beans.xml in .war and .jar modules.

Removing the beans.xml from war project solved the issue, but we are not sure where is the issue.

Thanks for your assistance.

Claudio

[_markus_]

Hi,

have you found any solution to this? I'm currently experiencing the same problem.....

thanks in advance

Markus

[mkouba]

Hi Claudio,

this is an EAP integration issue. Please raise a question on EAP discussions: https://community.jboss.org/en/jbosseap.