'ODI-40201: Cannot create the initial JNDI context' Signalled When a Failure Occurs on a JMS Server When Using ODI 11g Data Server URLs With Failover Syntax on Tibco or WebLogic Clusters Configured With JMS Distributed Destination

(Doc ID 1527421.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Data Integrator - Version 11.1.1.3.0 to 11.1.1.9.99 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

After setting up fallover type JNDI URLs for Oracle Data Integrator (ODI) 11g JMS Queue/Topic Data Servers implemented on Tibco or WebLogic server clusters configured with JMS Distributed Destination, and using the following syntax:

t3://node1:7001,node2:7002,node3:7003...

 or

t3://node1,node2,node3:7001

If the server t3://node1:7001 crashes for any reason, then ODI is unable to connect to server2 using the failover feature, and the following  message is signalled:

java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.
   at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
   at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
   at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.getConnection(OnConnectOnDisconnectDataSourceAdapter.java:74)
   ...

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