Error - OracleASjms/ESBMonitorTopic not Found on Startup of ESB Container
(Doc ID 432638.1)
Last updated on AUGUST 27, 2018
Applies to:Oracle ESB - Version 10.1.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Dec-2009***
***Checked for relevance on 16-May-2011***
You installed SOA suite 10.1.3.1, choosing J2EE & Web Server option in the installer and then created two OC4J containers - OC4J_BPEL & OC4J_ESB.
From supplement CDs, you installed BPEL & ESB into their corresponding OC4J containers created above. The installation went successfully and no errors were reported in the log.
BPEL projects are functioning as expected, but when ESB container is started, the following error is thrown in opmn log:
07/04/23 19:35:41 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
07/04/23 19:35:46 oracle.tip.esb.server.dispatch.QueueHandlerException: Context lookup failed
"OracleASjms/ESBMonitorTopic not found". Make sure the topic is mapped to a jndi tree
07/04/23 19:35:46 at oracle.tip.esb.server.dispatch.JMSEnqueuer.<init>(Unknown Source)
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|