My Oracle Support Banner

Following Additional Cluster Node Installation There Is An HTTP 404 Status Error And Application Server Log Message Failed To Parse Web.xml (Doc ID 1496590.1)

Last updated on FEBRUARY 22, 2021

Applies to:

Oracle WebCenter Sites - Version 7.6.0 and later
Information in this document applies to any platform.


Following upgrade one node in the cluster runs correctly alone, but when the second cluster node is running there is an HTTP 404 status error when trying to access a pagename in the environment.

The application server log of the second cluster node contains the following error:

"10:31:17,400 ERROR [MainDeployer] Could not initialise deployment: file:[...]/jboss-4.2/server/[server name]/deploy/cs.war/
org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: Invalid XML: file=file:[...]/jboss-4.2/server/[server name]/deploy/cs.war//WEB-INF/web.xml@3:192; - nested throwable: (org.xml.sax.SAXParseException: The element type "web-app" must be terminated by the matching end-tag "".))
at org.jboss.web.AbstractWebContainer.parseMetaData(
at org.jboss.web.AbstractWebContainer.init(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
  [trace continues]"



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

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