Changing Standalone Papi Client To Use Oracle JDBC Driver Throws ' java.lang.NoClassDefFoundError: com/ddtek/jdbc/extensions/ExtEmbeddedConnection' Error (Doc ID 1289966.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jul-2012***

Symptoms

The standalone PAPI clients were configured to use Oracle JDBC drivers instead of Datadirect Oracle drivers. After changing the directory.xml and removing DataDirect jars (b1base.jar, b1util.jar, and b1oracle.jar) from the classpath, the following error was received at runtime

Caused by: java.lang.NoClassDefFoundError: com/ddtek/jdbc/extensions/ExtEmbeddedConnection
  at fuego.jdbc.DatabaseManager.unlockConnection(DatabaseManager.java:91)
  at fuego.connector.impl.BaseJDBCConnector.createJDBConnection(BaseJDBCConnector.java:209)
  at fuego.jdbc.FaultTolerantConnection.createConnection(FaultTolerantConnection.java:921)
  at fuego.jdbc.FaultTolerantConnection.getConnection(FaultTolerantConnection.java:875)
  at fuego.jdbc.FaultTolerantConnection.prepareStatement(FaultTolerantConnection.java:545)
  at fuego.directory.provider.jdbc.JDBCPersistenceManager.getPreparedStatement(JDBCPersistenceManager.java:573)
  at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSchemaInfo(JDBCAuthenticationAccessor.java:149)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:585)
  at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
  at $Proxy10.getSchemaInfo(Unknown Source)
  at fuego.directory.provider.Factory.obtainSchemaInfo(Factory.java:557)
  at fuego.directory.provider.DirectorySessionImpl.loadSchemaInfo(DirectorySessionImpl.java:528)
  at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:245)
  at fuego.directory.provider.Factory.startSession(Factory.java:405)
  at fuego.directory.Directory.startAnonymousSession(Directory.java:214)
  at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:200)
  at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
  at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
  at fuego.papi.ProcessService.create(ProcessService.java:335)
  at com.fl.nk.bpm.util.BpmService.<init>(BpmService.java:56)
  at com.fl.nk.bpm.util.BpmService.refresh(BpmService.java:41)
  at com.fl.nk.bpm.util.BpmConnection.create(BpmConnection.java:47)
  at com.fl.nk.bpm.util.BpmConnection.create(BpmConnection.java:58)
  at com.fl.bpm.model.spi.fuego.FuegoProvider.createProcessInstance(FuegoProvider.java:58)
  ... 19 more

Changes

The BPM engine and directory configuration were modified to user Oracle JDBC drivers instead of Datadirect Oracle drivers.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms