My Oracle Support Banner

"Cannot find the target in JNDI" Message when Executing an ODI Integration Interface Which Loads a JMS Target Datastore (Doc ID 470155.1)

Last updated on OCTOBER 04, 2022

Applies to:

Oracle Data Integrator - Version 3.2.03.01 and later
Information in this document applies to any platform.

Symptoms

When executing an Integration Interface having a JMS Topic target Datastore, Oracle Data Integrator (ODI) 10g and 11g attempts to connect to an incorrect JMS Destination.
More specifically, ODI attempts to connect to "/jms/<Topic Name>" instead of "jms/<Topic Name>", as defined on the MOM (OC4J for example). Notice the prefix "/" added by ODI.

Note:<Topic Name>  is the name of the Topic

Following message is signaled:

java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (/jms/demoTopic)
at com.sunopsis.jdbc.driver.bh.executeUpdate(bh.java)
at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)

A similar message is also displayed when:
  • Consulting the Data stored in the Queue / Topic (right-click > Data on the JMS Datastore).
  • The Datastore is on "JMS Queue", "JMS Queue XML", "JMS Topic" or "JMS Topic XML" Technology.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.