Migration Application Not Opening due to Tomcat Errors "The element type " " must be terminated by the matching end-tag"
(Doc ID 2900328.1)
Last updated on OCTOBER 04, 2022
Applies to:
Siebel CRM - Version 21.4 and laterInformation in this document applies to any platform.
Symptoms
While attempting to connect to the migration application the login page will not load.
When trying to redeploy the migration profile, it fails giving a red mark.
Errors observed in catalina.out:
28-Sep-2022 00:18:25.565 SEVERE [main] org.apache.tomcat.util.digester.Digester.fatalError Parse fatal error at line [220] column [3]
org.xml.sax.SAXParseException; systemId: file:/D:/Siebel/AI/applicationcontainer_external/webapps/siebel/WEB-INF/web.xml; lineNumber: 220; columnNumber: 3; The element type "error-page" must be terminated by the matching end-tag "</error-page>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178)
org.xml.sax.SAXParseException; systemId: file:/D:/Siebel/AI/applicationcontainer_external/webapps/siebel/WEB-INF/web.xml; lineNumber: 220; columnNumber: 3; The element type "error-page" must be terminated by the matching end-tag "</error-page>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178)
Steps to replicate the issue:
1. Restart the entire application.
2. Enter the migration URL to connect.
3. Server Busy error is being given.
Changes
It was found that there were changes at web.xml level that were incomplete:
and "</error-page>" was missing at the end of the above entry.
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 |