JBoss AS 7.1.0 + Hibernate 3

[Rodrigo Sasaki]

Hello everyone,

I used to run a project on GlassFish with Hibernate 3, and it all worked fine.

But then we switched to JBoss AS 7.1.0 (Thunder), and it goes with Hibernate 4 by default, until then all is OK.

But on some queries on the system a Hibernate exception is being thrown...

Something about an assertion failure, that says it might be a Hibernate bug, and I believe it really is (since it worked on Hibernate 3).

I was wondering if I could run my JBoss AS 7.1 with Hibernate 3, changing the modules somehow..

Can anybody help me to do it?

Thanks!

[Rodrigo Sasaki]

OK, doing some testing I think I'm getting there..

I added the line below to my persistence.xml file:

<property name="jboss.as.jpa.providerModule" value="org.hibernate:3"/>

I created my module on the following folder:

%JBOSS_HOME%\modules\org\hibernate\3

under the 3 folder I have the hibernate3.jar and the module.xml, that looks like this:

<?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="org.hibernate" slot="3"> <resources> <resource-root path="hibernate3.jar"/> </resources> <dependencies> <module name="org.jboss.as.jpa.hibernate" slot="3"/> <module name="asm.asm"/> <module name="javax.api"/> <module name="javax.persistence.api"/> <module name="javax.transaction.api"/> <module name="javax.validation.api"/> <module name="org.antlr"/> <module name="org.apache.ant"/> <module name="org.apache.commons.collections"/> <module name="org.infinispan"/> <module name="org.javassist"/> <module name="org.slf4j"/> <module name="org.dom4j"/> </dependencies> </module>

but when I try to start the server I get the following error:

15:09:51,096 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (MSC service thread 1-3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:447)
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:385)
	at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:758)
	at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:343)
	at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:400)
	at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
	at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
	at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368)
	at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
	at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129)
	at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:71) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:113) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2863) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2859) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1870) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:906) [hibernate3.jar:3.6.10.Final]
	at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) [hibernate3.jar:3.6.10.Final]
	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final]
	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) [jboss-as-jpa-7.1.0.Final.jar:7.1.0.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
Caused by: javax.resource.ResourceException: Could not find accessor on XADataSource: 
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:629)
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430)
	... 23 more
Caused by: java.lang.NoSuchMethodException: oracle.jdbc.xa.client.OracleXADataSource.setUrl(java.lang.String)
	at java.lang.Class.getMethod(Class.java:1605) [rt.jar:1.6.0_25]
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:597)

As you can see a NoSuchMethodException is being thrown, but I don't know why.. I have the oracle driver configured correctly, it worked on default Hibernate4 configurations.

I defined the driver with the following lines on my standalone.xml:

<datasources> ... <drivers> ... <driver name="oracle" module="com.oracle.ojdbc6"> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> </driver> </drivers> </datasources>

does anybody know why this error is happenning?

Thanks!

[James Boswell]

Rodrigo

I am trying to do this at moment. If and when I get it working, I will let you know.

[Rodrigo Sasaki]

Thanks, James.

I'll keep trying here too, and I'll post whatever news I find helpful

[Rodrigo Sasaki]

I think my configuration worked..

the problem I'm having is happening even on default Hibernate 4 configurations...

I don't know what caused this problem, maybe someone changed something on the server..

But I believe the Hibernate 3 Configuration has worked, if you (James) want to try out what I did, though I can't test it while I still have this problem.

[Rodrigo Sasaki]

It works, James

You can do what I posted up there...

[James Boswell]

Rodrigo

I have tried your module.xml but each time, I attempt to deploy my web application (as a WAR), the output on JBoss reads:

13:36:17,881 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "health-plan-app.war"
13:36:21,914 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry iText-toolbox.jar in "<JBOSS_HOME>/bin/content/health-plan-app.war/WEB-INF/lib/itext-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
13:36:21,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry iText-toolbox-2.1.5.jar in "<JBOSS_HOME>/bin/content/health-plan-app.war/WEB-INF/lib/itext-2.1.5.jar" does not point to a valid jar for a Class-Path reference.
13:36:22,633 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
13:36:22,646 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

Nothing further happens until the deployment times out. I have increased the default timeout of 60 seconds but to no avail.

I am not using a persistence.xml but my application still relies on Hibernate 3 so an entry in health-plan-app.war/META-INF/MANIFEST.MF reads:

Dependencies: org.hibernate:3

Apart from creating the module, was there any other configuration required on JBoss?

[Rodrigo Sasaki]

actually no.. all I did was creating the new module, with all the dependencies that it required..

and adding the reference to it as my jpaProvider on my persistence.xml

I didn't really change the MANIFEST.MF, don't know if that actually makes a difference..


but it looks like you're having trouble with different jar files aren't you? not the hibernate config