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 JANUARY 04, 2016

Applies to:

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

Symptoms

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(AbstractWebContainer.java:755)
at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
  [trace continues]"

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms