Problems using Hibernate 3.6 with WildFly

[mylos78]

Dear all,

I need some help with one web application which bundles the following Hibernate 3.6 libraries in the WEB-INF/lib folder:

I've added the following persistence.xml which has the property jboss.as.jpa.providerModule set to "hibernate3-bundled".

<persistence version="2.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_2_0.xsd">
   <persistence-unit name="primary">

      <jta-data-source>java:jboss/datasources/MySQLDS</jta-data-source>
      <properties>
         <!-- Properties for Hibernate -->
         <property name="hibernate.hbm2ddl.auto" value="create-drop" />
         <property name="hibernate.show_sql" value="false" />
         <property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />
      </properties>
   </persistence-unit>
</persistence>

Once deployed, however the application issues the following exception:

14:36:03,478 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"aem.war\".FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"aem.war\".FIRST_MODULE_USE: JBAS018733

: Failed to process phase FIRST_MODULE_USE of deployment \"aem.war\"

    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:

JBAS011434: Persistence provider module load error application (class org.hibernate.jpa.HibernatePersistenceProvider)

    Caused by: org.jboss.modules.ModuleNotFoundException: application:main"}}

14:36:03,522 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "aem.war" with deployment "aem.war"

14:36:03,524 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

JBAS014777:   Services which failed to start:      service jboss.deployment.unit

."aem.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xalan.war".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "aem.war"

The exception ModuleNotFound lead me to think that it looks for Hibernate 3.6 into the application server modules, however in the WildFly-JPA migration guide it's not mentioned to install Hibernate 3.X as well.

Any clue ?

Thanks!

[ctomc]

org.jboss.modules.ModuleNotFoundException: application:main

that means that it is looking for module named "application"

it would guess that you must have some mistake in jboss-deployment-structure.xml or MANIFEST.MF

[mylos78]

Thanks for the reply. Well I have added in jboss-deployment-structure.xml the following to exclude the default hibernate libs:

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">

  <deployment>
    <exclusions>
      <module name="org.hibernate"/>
    </exclusions>
  </deployment>

</jboss-deployment-structure>

However the exception has not changes. Still the same :-(

[smarlow]

Could you try removing some extra jars from your deployment.  Try removing hibernate-jpa-2.0-api-1.0.1.Final.jar, javassist-3.1.2.0.GA.jar, jta-1.1.jar, slf4j-api-1.6.1.jar.

The unit test that does the same thing (with fewer jars included) is at.  Rather than use the hibernate3.jar, we included individual Hibernate jars but I don't think that is your issue.

[smarlow]

Also, let us know which version of WildFly you are using.  Nightly builds are available at this link, so you can try the latest.

[f_marchioni]

Hi,

my guess is that the persistence.xml is wrong, to be precise you need to use the older provider class which is in Hibernate 3.X. See the following example (adapt the datasource name):

<persistence 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_2_0.xsd"

         version="2.0">

   <persistence-unit name="primary">

      <provider>org.hibernate.ejb.HibernatePersistence</provider>

      <jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>

      <properties>

         <!-- Properties for Hibernate -->

         <property name="hibernate.hbm2ddl.auto" value="create-drop" />

         <property name="hibernate.show_sql" value="false" />

         <property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />

      </properties>

   </persistence-unit>

</persistence>

Hope it helps

Francesco

[smarlow]

Yeah, this makes sense also (test case linked above is using <provider>org.hibernate.ejb.HibernatePersistence</provider>).  We are likely to use the default persistence provider name otherwise, which is now different.

I still think that removing the interface jars that I mentioned above will also help.

[mylos78]

By changing the provider version it worked! I was able to complete the first application test successfull! I'll consider removing the jar mentioned by Scott if any issues arises in the other tests. Thanks all for your help.