"Document is invalid: no grammar found." Errors on Services.xml Attempting to Start Web Server After Applying EPM 8.0.7.4 ML
(Doc ID 2736862.1)
Last updated on MAY 17, 2023
Applies to:
Oracle Financial Services Asset Liability Management - Version 8.0.7.4.0 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)
Maintenance Level (ML) Patch
Apache Tomcat
Weblogic
WebSphere
Symptoms
After installing patch 31465972 - ALM 8074 and deploying it in Tomcat, the service re-start is failing. Further investigation indicated that the issue is caused by a malformed XML for services.xml, which was traced from the install folder p31465972/OFS_ALM_PACK/OFS_ALM/bin/ficweb/webroot/WEB-INF/classes/services.xml. There are a couple of issues that had to be manually fixed in this file:
1. There's an extra closing tag.
2. Missing DOCTYPE
ERROR
21-Sep-2020 07:29:48.283 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.filterStart Exception starting filter [struts2]
Unable to load configuration. - include - file:/opt/tomcat85/webapps/ofsaa/WEB-INF/classes/struts.xml:17:34
at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:504)
...
... 17 more
Caused by: Document is invalid: no grammar found. - file:/opt/tomcat85/webapps/ofsaa/WEB-INF/classes/services.xml:1:9
at com.opensymphony.xwork2.util.DomHelper.parse(DomHelper.java:119)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:1021)
... 22 more
Caused by: org.xml.sax.SAXParseException; systemId: file:/opt/tomcat85/webapps/ofsaa/WEB-INF/classes/services.xml; lineNumber: 1; columnNumber: 9; Document is invalid: no grammar found.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
The issue can be reproduced at will with the following steps:
1. Apply ALM 8.0.7.4 patch 31465972 in instance with FTP and ALM
2. Attempt to redeploy
Changes
Apply 8.0.7.4 ML patches:
<Patch 31465972> OFS Asset Liability Management Application Pack (OFSALM) Release 8.0.7.4.0
<Patch 31562932> OFS Profitability Management Application Pack (OFSPFT) Release 8.0.7.4.0
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 |
| References |