javax.naming.AuthenticationException When Java Client Performing OC4J JMS Queue and LDAP lookup (Doc ID 1531042.1)

Last updated on APRIL 29, 2017

Applies to:

Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
JDBC - Version 10.1.0.5 to 11.2.0.4.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.

Symptoms

 

A Siebel Client sends Java Message Service (JMS) message based on 10.1.3.5  OC4J JMS Queue.
This OC4J Queue is configured so that JMS message is sent to persistent Oracle database Queue (AQ).
Siebel uses jndi.properties file in order to lookup Queue factory and Queue which are configured at the oc4j level.

Example :

The problem is that Siebel cannot send JMS message (to Oracle Database Server Queue ) when the datasource related to the JMS provider queue is using LDAP to store JDBC URL to connect to the Oracle database server.

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