OC4J AppClient Looking Up an AQ JMS Resource Provider Returns NoClassDefFoundError

(Doc ID 949133.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version: and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.


Running an application client against OC4J which looks up an AQ JMS resource provider via JNDI, it works fine when the AQ JMS provider is configured to use a direct JDBC URL.

But when it is configured to use a datasource, it fails with:

java.lang.NoClassDefFoundError: org/apache/bcel/generic/Instruction
   at oracle.oc4j.sql.spi.ConnectionHandle.getConnectionHandle(ConnectionHandle.java:670)


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