WildFly 28 -> 35 upgrade with hibernate configured with hibernate.jndi.class

[Lawrence Sim]

Hey,

We are upgrading the version of WildFly that we are deploying our EAR to from WildFly (28.0.1) -> (35.0.1).

We have hibernate persistence configuration in a JAR within the EAR lib folder that is being picked up.

Each persistence-unit contains the hibernate.jndi.class property that points to our own class that implements InitialContextFactory.

Previously WildFly 28 would log:

Finding class package.MyInitialContextFactory from Module "deployment.app.ear" from Service Module Loader

WildFly 35 now logs

Finding class  package.MyInitialContextFactory from Module "org.jboss.as.jpa" version 35.0.1.Final from local module loader

WildFly seems to be trying to pull the class from the wrong Module, any ideas?

Regards,

Lawrence

[Scott Marlow]

Please add the full exception call stack which might give a hint as to which Hibernate ORM class to look at.  I looked at the "hibernate.jndi.class" property use in Hibernate ORM 6.6 and that wasn't helpful.

Why are you using the "hibernate.jndi.class" property?  Are you using a custom database connection pool library?  I'm curious as to what your use case is for "hibernate.jndi.class".

Regards,

Scott

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/c1bbc3e5-fca7-4182-a77a-507a7fb130bbn%40googlegroups.com.