OC4J AppClient Looking Up an AQ JMS Resource Provider Returns NoClassDefFoundError
(Doc ID 949133.1)
Last updated on MARCH 02, 2019
Applies to:Oracle Containers for J2EE - Version 10.1.3.4.0 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:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document