NameNotFoundException in SOA server logs after upgrading a domain from SOA 11g to SOA 12.1.3 (Doc ID 2051623.1)

Last updated on AUGUST 16, 2024

Applies to:

Oracle SOA Suite - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

After upgrade of the domain from SOA11g to SOA 12.1.3, the following errors appear in the logs when starting the SOA Servers:

- The SOA server diagnostic log contains:

[2015-04-15T17:13:50.483+02:00] [server] [ERROR] [SDP-25717] [oracle.sdpinternal.messaging.util.MessagingUtil] [tid: [STANDBY].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: ] [APP: usermessagingserver] Error occurred in looking up Queue in JNDI, skipping: OraSDPM/Queues/OraSDPMAppDefRcvQ1. [[
javax.naming.NameNotFoundException: While trying to lookup 'OraSDPM.Queues.OraSDPMAppDefRcvQ1' didn't find subcontext 'Queues'. Resolved 'OraSDPM'; remaining name 'Queues/OraSDPMAppDefRcvQ1'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:265)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:253)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at oracle.sdpinternal.messaging.util.MessagingUtil.getQueueInfoList(MessagingUtil.java:1212)
...

This error also occurs for other queues, for example: OraSDPM.Queues.OraSDPMEngineSndQ1, OraSDPM.Queues.OraSDPMEngineRcvQ1, OraSDPM.Queues.OraSDPMEnginePendingRcvQ, OraSDPM.Queues.OraSDPMEngineRcvQ1

The SOA server log contains:

#### <> <> The destination for the MessageDrivenBean MessageDispatcherBean(Application: usermessagingserver, EJBComponent: parlayx-ejb.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name OraSDPM/Queues/OraSDPMWSRcvQ1. The EJB container will periodically attempt to resolve this MessageDrivenBean destination and additional warnings may be issued.>

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

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

NameNotFoundException in SOA server logs after upgrading a domain from SOA 11g to SOA 12.1.3 (Doc ID 2051623.1)

Applies to:

Symptoms

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!