My Oracle Support Banner

Unable to login to OFSAA application after switching from Weblogic to Tomcat (Doc ID 2719001.1)

Last updated on FEBRUARY 27, 2022

Applies to:

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

Symptoms

On : 8.0.4 version, Administration_OFSS

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

ERROR
-----------------------
UMMService.log
[UMMLOG] Sep 30,20 20:07:47 : [LOGGER]Cannot create JDBC driver of class '' for connect URL 'null'
java.sql.SQLException: Cannot create JDBC driver of class '' for connect URL 'null'
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:2160)
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:2032)
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1532)
at com.iflex.reveleus.db.connection.Connections.getTomcatConnectionFromPool(Connections.java:103)
at com.iflex.reveleus.db.connection.Connections.getConnection(Connections.java:66)
at com.iflex.reveleus.db.connection.DBConnectionFactory.getConnection(DBConnectionFactory.java:68)
at com.iflex.reveleus.form.util.NewFormRendererCache.reloadSTDFormMap(NewFormRendererCache.java:1400)
at com.iflex.reveleus.form.servlets.AJAXServlet.init(AJAXServlet.java:131)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1227)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1140)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1027)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5038)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5348)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1816)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
at java.util.concurrent.FutureTask.run(FutureTask.java:277)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:785)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:326)
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:2144)
... 24 more



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