Lookup() In Initialcontext Fails With Exception (Doc ID 1296439.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Weblogic Server - Version: 10.3.3 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

In the context of  WebLogic Server 10.3.3.0.0 running on top of
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.6.0_20-b02

The issue is about
- an application deployed on Weblogic.
- It gives servlet failed errors.
- All other servlets are working fine


####<Feb 12, 2011 1:17:34 AM IST> <Debug> <DTF> <...> <...> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1297453654516> <BEA-000000> <dynamic tag request from .../...:...>
####<Feb 12, 2011 1:17:34 AM IST> <Error> <DTF> <...> <...> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1297453654517> <BEA-000000> <dynamic tag execution failed!
java.lang.RuntimeException: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at ...Servlet.initUserTransaction(...Servlet.java:134)

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