"Could not initialize class com.arjuna.ats.internal.jts.OTSImpleManager" in SOA-P
Issue
- Migrated from SOA 5.2.0 to 5.3.1
-
Encountering an error during startup/application deployment
... FATAL loggerI18N:96 - [com.arjuna.ats.internal.jts.ORBManager] The ORB has not been initialized yet ... ... org.jboss.util.NestedSQLException: Error checking for a transaction.; - nested throwable: (java.lang.reflect.UndeclaredThrowableException); - nested throwable: (org.jboss.resource.JBossResourceException: Error checking for a transaction.; - nested throwable: (java.lang.reflect.UndeclaredThrowableException)) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102) at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.initDatabase(DatabaseInitializer.java:96) at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.startService(DatabaseInitializer.java:159) ... Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:344) ... java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.internal.jts.OTSImpleManager
Environment
- Red Hat JBoss Enterprise SOA Platform (SOA-P) 5.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.