Resolution:
Description:
===========
In TIBCO BusinessEvents, having multiple versions of Oracle drivers within the classpath may lead to incompatible jars being used with the running Java version .

Environment:
===========
All Operating Systems
TIBCO BusinessEvents 4.x,5.x

Symptoms:
===========
com.tibco.cep.runtime.model.exception.impl.BEExceptionImpl: java.lang.AbstractMethodError: oracle.jdbc.driver.T4CPreparedStatement.isClosed()Z

Root Cause:
===========
The above error indicates that the oracle driver jar file does not contain the method isClosed for the class oracle.jdbc.driver.T4CPreparedStatement . Hence the appropriate jar file needs to be used .Having multiple versions of Oracle drivers within the classpath may cause be-engine to use incompatible jar files for the version of Java running .

Resolution:
===========
Steps to find out which jar files are loaded in the startup of the BE engine:

Append " --debug &gtdebug.out" when starting the BE engine. In this way all of the jars loaded by engine will be logged to the debug.out file. For example, be-engine --propFile BE_HOME\bin\be-engine.tra -u default -c FraudDetection/fd.cdd fd.ear --debug &gtdebug.out or append –verbose:class to the existing java.extended.properties in be-engine.tra

- Search for ojdbc6.jar or classes12.jar or ojdbc14.jar in the debug.out to find all occurrences.

If more than one occurrence is found in the classpath, keep only ojdbc6.jar in the class path and move the other jars out of the class path if using Java 1.6 . Similarly, if using Java 1.4 keep only ojdbc14.jar in the classpath and for Java 1.2 make sure only classes12.jar is in the classpath .