jboss-6.0.0.Final: Unable to process @Resource annotation (title changed)

[abhi0123]

Hi,

Fed up from vendor lock in and pushy not so intelligent support, and hopeful from the ever growing JBoss fanbase, we started a new development project on JBoss 5.1.0.GA. We are using JBoss 5.x because we want to stick to Java EE 5 for some more time. If it matters, we are using Mainframe DB2 server.

I only found a similar problem as mine but the solution did not work for me. Please help.

http://community.jboss.org/message/533636

Server log:

Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:483)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4388)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
... 74 more
Caused by: java.lang.NullPointerException
at org.jboss.injection.PersistenceUnitHandler.getManagedEntityManagerFactory(PersistenceUnitHandler.java:149)
at org.jboss.injection.PcEncInjector.inject(PcEncInjector.java:76)
at org.jboss.web.tomcat.service.TomcatInjectionContainer.populateEnc(TomcatInjectionContainer.java:482)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:471)
... 77 more
2011-02-17 21:30:37,561 INFO  [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-1) Failed to complete command: [start] for deployment: names=[vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/reporting.war/], copyContent=true
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/reporting.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/C:/jboss-5.1.0.GA/server/default/tmp/a18b2w-m9yq71-gkahbb86-1-gkahg04r-ij/reporting.war/ deployment failed

persistence.xml:

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="abcPU" transaction-type="JTA">
  <provider>org.hibernate.ejb.HibernatePersistence</provider>
  <jta-data-source>java:TEST</jta-data-source>
  <properties>
   <property name="hibernate.hbm2ddl.auto" value="validate" />
   <property name="hibernate.show_sql" value="true" />
   <property name="hibernate.dialect" value="org.hibernate.dialect.DB2Dialect" />
   <property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory" />
   <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />  
  </properties> 
</persistence-unit>

</persistence>

db2-ds.xml:

<?xml version="1.0" encoding="UTF-8"?>

<datasources>
<local-tx-datasource>
  <jndi-name>TEST</jndi-name>
  <connection-url>jdbc:db2://MVST:50000/TEST</connection-url>

  <driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
  <user-name>x</user-name>
  <password>y</password>
  <min-pool-size>0</min-pool-size>

  <!-- New org.jboss.resource.adapter.jdbc.vendor.DB2ExceptionSorter -->
  <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DB2ExceptionSorter
  </exception-sorter-class-name>

  <!-- sql to call on an existing pooled connection when it is obtained from
   pool -->
  <check-valid-connection-sql>SELECT 1 FROM TABLE1
  </check-valid-connection-sql>
  <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
  <metadata>
   <type-mapping>DB2</type-mapping>
  </metadata>
</local-tx-datasource>

</datasources>

[jaikiran]

Can you please post/attach the entire log that you see on the console? By the way, where have you placed these persistence.xml and the db2-ds.xml files?

[wdfink]

I'm not sure but

<jta-data-source>java:TEST</jta-data-source>

might not work, I use it like

<jta-data-source>java:/TEST</jta-data-source>

[jaikiran]

abhi0123 wrote:

We are using JBoss 5.x because we want to stick to Java EE 5 for some more time. If it matters, we are using Mainframe DB2 server.

By the way, I will still recommend using JBoss AS 6.0.0.Final because there have been numerous bug fixes and performance improvements after JBoss AS 5.1.0 was released. JBoss AS6 has Java EE 6 support but that doesn't mean that you will have to use the new features if you don't want to. Java EE 6 is backward compatible, so your Java EE 5 application should very well work on JBoss AS6 too.

[abhi0123]

jaikiran pai wrote:

... JBoss AS6 has Java EE 6 support but that doesn't mean that you will have to use the new features if you don't want to. Java EE 6 is backward compatible, so your Java EE 5 application should very well work on JBoss AS6 too.

My understanding is JBoss AS 6.0.0.Final ships with Java EE 6, Servlet 3.0 and JPA 2.0 support. We are on Java EE 5, Servlet 2.5 and JPA 1.0. Where can I find these dependencies? I am using the following repositories and I don't see these dependencies there.

http://repository.jboss.org/nexus/content/groups/public

http://repository.jboss.org/nexus/content/groups/public-jboss

[abhi0123]

jaikiran pai wrote:

Can you please post/attach the entire log that you see on the console? By the way, where have you placed these persistence.xml and the db2-ds.xml files?

Attached log.

db2-ds.xml is in %JBOSS_HOME%\server\default\deploy. persistence.xml is in WEB-INF\classes\META-INF.

[abhi0123]

After deploying in JBoss AS 6.0.0.Final, I am getting a different exception:

DEPLOYMENTS IN ERROR:

Deployment "vfs:///C:/jboss-6.0.0.Final/server/default/deploy/reporting.war" is in error due to the following reason(s): java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref named env/applicationParameterManager of type <<package>>.ApplicationParameterManager

From what I figure, it does not like the following Spring configuration. Why?

@Configuration

public class SecurityConfig {

    @Autowired

    private ProviderManager authenticationManager;

    @Resource(name = "applicationParameterManager")

     private ApplicationParameterManager applicationParameterManager;

...

}

[jaikiran]

There's some class which is injecting (either through res-env-ref or through @Resource annotation) some resource of type ApplicationParameterManager. What does that code look like? And please post the entire exception stacktraces.

[jaikiran]

Hmm, so it ends up picking up some Spring class which uses that @Resource annotation.

Where is this class located? In which jar? And where in the .war is this .jar file located?

[abhi0123]

jaikiran pai wrote:

Hmm, so it ends up picking up some Spring class which uses that @Resource annotation.

Where is this class located? In which jar? And where in the .war is this .jar file located?

ApplicationParameterManager is an application class which I annotated as @Resource. It is present in WEB-INF/classes/<<package>>.

Log attached.

[abhi0123]

Is there no one who can help me out?

[jaikiran]

I can think of some workaround to this issue, but I would like to know a bit more about your application. Do you want any annotation scanning to take place for your application? If you are OK with disabling annotation scanning for that .war file, then we can set the metadata-complete to true in the web.xml and get past this issue.

The problem here is that the @Resource is a Java EE annotation which the servlet container ends up picking up. And since the @Resource isn't complete (i.e. it is missing some info), the container throws this error.

[abhi0123]

jaikiran pai wrote:

Do you want any annotation scanning to take place for your application?

Yes, I do want annotation scanning to take place for my application.

jaikiran pai wrote:

The problem here is that the @Resource is a Java EE annotation which the servlet container ends up picking up. And since the @Resource isn't complete (i.e. it is missing some info), the container throws this error.

That sounds like a serious bug to me. Why should the Web container be messing with code it has no business dealing with at the first place?

[jaikiran]

https://issues.jboss.org/browse/JBAS-8775 (I forgot to add the details to that JIRA, will do it tonight).

[jaikiran]

As a workaround, try adding this jboss-web.xml to your .war/WEB-INF folder:

<?xml version="1.0"?>

<!DOCTYPE jboss-web PUBLIC
        "-//JBoss//DTD Web Application 5.0//EN"
        "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd">


<jboss-web>

            <resource-env-ref>
                <resource-env-ref-name>applicationParameterManager</resource-env-ref-name>
                <jndi-name>dummyJNDIName</jndi-name>
                <ignore-dependency/>
            </resource-env-ref>

</jboss-web>

Let us know if that gets you past this issue.