My Oracle Support Banner

'Invalid Request' After Logging into OFSAA and ERROR Could not parse file RevLog4jConfig.xml (Doc ID 2530771.1)

Last updated on MAY 03, 2019

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.0 to 8.0.5 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA) 8.0 - 8.0.5, after logging in, you get the error below instead of the expected user interface:

Invalid Request / Error while processing request

The following errors exist in the Websphere nohup.out / SystemErr.log:

[4/8/19 18:41:21:967 EEST] 000000eb SystemErr R log4j:WARN Fatal parsing error 33 and column 26
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R log4j:ERROR Could not parse file [/WebSphere/profiles/<app server>/installedApps/<app>/<app>.ear/<app>.war/conf/RevLog4jConfig.xml].
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R org.xml.sax.SAXParseException: Attribute name "value" associated with an element type "param" must be followed by the ' = ' character.
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.DOMConfigurator$1.parse(DOMConfigurator.java:598)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:604)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:861)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:88)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.helpers.FileWatchdog.(FileWatchdog.java:57)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.XMLWatchdog.(DOMConfigurator.java:853)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at org.apache.log4j.xml.DOMConfigurator.configureAndWatch(DOMConfigurator.java:584)
[4/8/19 18:41:21:968 EEST] 000000eb SystemErr R at com.iflex.fic.common.Log4jLogger.init(Log4jLogger.java:78)
[4/8/19 18:41:21:969 EEST] 000000eb SystemErr R at com.iflex.fic.common.Log4jLogger.initializeLog4j(Log4jLogger.java:54)
[4/8/19 18:41:21:969 EEST] 000000eb SystemErr R at com.iflex.fic.ficml.FICMaster.init(FICMaster.java:131)
[4/8/19 18:41:21:969 EEST] 000000eb SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:345)
[4/8/19 18:41:21:969 EEST] 000000eb SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
[4/8/19 18:41:21:969 EEST] 000000eb SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1369)

Due to this issue, you cannot use 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


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