My Oracle Support Banner

Unable to access application after switching webserver from Weblogic to Tomcat (Doc ID 2723598.1)

Last updated on MARCH 04, 2022

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.7 and later
Information in this document applies to any platform.

Symptoms

On : 8.0.7 version, Administration_OFSS

When attempting to access application after switching from Weblogic to Tomcat
the following error occurs.

ERROR
-----------------------

Below error was noticed in Catalina.out

javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at com.iflex.fic.util.Connections.getWebLogicConnectionFromPool(Connections.java:257)
at com.iflex.fic.util.Connections.getDBConnection(Connections.java:141)
at com.ofss.fccm.fraud.db.DBConnection.getConnection(DBConnection.java:66)
at com.ofss.fccm.fraud.db.DBConnection.executeQuery(DBConnection.java:84)
at com.ofss.fccm.fraud.main.ProcessCronJob.run(ProcessCronJob.java:36)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)

.....
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory

.....
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1358)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1180)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:91)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:61)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:672)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Try to access application after switching from Weblogic to Tomcat

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access the application.



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
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.