Search code examples
javaweblogic11g

Persistence Issue for JPA 2.0 on Weblogic


We were trying to deploy an Application on Weblogic and are getting the below error while Activating Changes. I have done the necessary setup for activating JPA 2.0. If you need further details do let me know and I will share the same. Has anyone faced this before??

 java.lang.AbstractMethodError:
 weblogic.deployment.PersistenceUnitInfoImpl.getValidationMode()Ljavax/persistence/ValidationMode;
         at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:633)
         at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:386)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.<init>(BasePersistenceUnitInfoImpl.java:158)
         Truncated. see log file for complete stacktrace
 Caused By: java.lang.AbstractMethodError:
 weblogic.deployment.PersistenceUnitInfoImpl.getValidationMode()Ljavax/persistence/ValidationMode;
         at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:633)
         at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:386)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.<init>(BasePersistenceUnitInfoImpl.java:158)
         Truncated. see log file for complete stacktrace

The weblogic version I can see on the console is as below

WebLogic Server 10.3.6.0.4 PSU Patch for BUG16083651 Thu Mar 28 15:24:29 IST 2013 WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050


Solution

  • It was a code compatibility problem between the Development and Weblogic version. Downgrading the WebLogic version to 10.3.6.0 resolved the issue.