My Oracle Support Banner

Failed To Load Work Manager With SIP Message Logging Enabled: javax.naming.NameNotFoundException (Doc ID 1195083.1)

Last updated on AUGUST 27, 2020

Applies to:

Oracle Communications Converged Application Server - Version 4.0.0 to 5.0.0 [Release 4.0.0 to 5.0]
Information in this document applies to any platform.
***Checked for relevance on 02-Apr-2013***

Symptoms

With SIP message logging servlet deployed, which implements com.bea.wcp.sip.engine.server.MessageListener interface, after invoking SipServletResponse.send(), javax.naming.NameNotFoundException is thrown when calling InitialContext.lookup("java:comp/env/wm/MyWorkManager").

  InitialContext.lookup() should use com.bea.wcp.sip.naming.SipJavaURLContext as context.
While after invoking SipServletResponse.send(), InitialContext.lookup() is using weblogic.jndi.factories.java.javaURLContextFactory$JavaURLContext.

The full error stack looks like below:

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.