My Oracle Support Banner

Unable To Login To OFSAA UI (Doc ID 3071026.1)

Last updated on FEBRUARY 12, 2025

Applies to:

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

Symptoms

On: OFSAAI 8.1.2.2.0 Version.

OFSAA Login page popup is not coming due to unable to connect to UI.

The catalina.out from Deployed location following the below error.

LOG FILE
-----------------------
Filename = Catalina. Out
See the following error:

30-Jan-2025 12:10:39.334 INFO [Thread-10] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.apache.naming.NamingContext]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.apache.naming.NamingContext]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1349)
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1337)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1174)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1141)
at org.apache.logging.log4j.util.LoaderUtil.loadClass(LoaderUtil.java:167)
at org.apache.logging.log4j.core.impl.ThrowableProxyHelper.loadClass(ThrowableProxyHelper.java:214)

Verified this issue the OFSA log in UI screen reviewing the log in the F12 developer screen, we identified the following error.

"Refused to execute inline script because it violates the following Content Security Policy directive: 'script-src 'self''. Either the 'unsafe-inline' keyword, a hash ('sha256-4StxPwOUk8Iidsp1kLYiJKZW1hH2Vj7Op6XnJvsKzQo='), or a nonce ('nonce-...') is required to enable inline execution."

Changes

 No 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


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