Tomcat fails to start: "Parse Fatal Error"

Refers to:

  • Plesk 11.5 for Linux
  • Plesk 12.0 for Linux

Created:

2016-11-16 12:44:07 UTC

Modified:

2017-02-03 06:17:14 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Tomcat fails to start: "Parse Fatal Error"

Symptoms

Tomcat service fails to start with following errors in /var/log/tomcat6/catalina.out

Oct 28, 2013 3:23:10 PM org.apache.tomcat.util.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException; systemId: file:///usr/share/tomcat6/conf/server.xml; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)

Oct 28, 2013 10:30:18 PM org.apache.catalina.startup.Catalina load
WARNING: Catalina.start using conf/server.xml:
org.xml.sax.SAXParseException; systemId: file:///usr/share/tomcat6/conf/server.xml; lineNumber: 21; columnNumber: 87; Error at (21, 87: org.apache.catalina.storeconfig.StoreConfigLifecycleListener
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2806)
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2832)

Cause

File server.xml is not well-formed or contains values not compatible with Tomcat 6 .

For example, following line may be the reason of the issue. This line may be used for Tomcat 5 , but causes an error for Tomcat 6

<Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>

Resolution

Check the lines specified in the errors. Compare those values to the attached sample server.xml file.

Have more questions? Submit a request
Please sign in to leave a comment.