[Philip Copeland]

Hi Guys,

I’m having a few problems deploying an app to Tomcat (4.24?) with the latest build 3.7.2.

Here is the exception that is getting thrown by Tomcat as soon as I deploy

Any suggestions – this was working fine with the previous release.

Thanks

Philip
———————————————————–

Apr 11, 2004 6:09:27 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8000
Starting service Tomcat-Standalone
Apache Tomcat/4.1.30
Apr 11, 2004 6:09:28 PM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config=’org.apache.struts.util.LocalStrings’, returnNull=true
Apr 11, 2004 6:09:28 PM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config=’org.apache.struts.action.ActionResources’, returnNull=true
Apr 11, 2004 6:09:29 PM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config=’org.apache.webapp.admin.ApplicationResources’, returnNull=true
Apr 11, 2004 6:09:31 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8000
Apr 11, 2004 6:09:31 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Apr 11, 2004 6:09:31 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/81 config=C:\Program Files\Apache Group\Tomcat 4.1\conf\jk2.properties
Apr 11, 2004 6:10:16 PM org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3587)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:821)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:307)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:788)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:559)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:401)
at org.apache.catalina.startup.HostConfig.run(HostConfig.java:851)
at java.lang.Thread.run(Thread.java:534)

[Riyad Kalla]

Based on this:

SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog

and this:

at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)

I’m thinking something is wrong with your server.xml file, and this specific context (invalid content somewhere). Can you open this file with MyEclipse, right click, and do a “Validate” and see what comes up?

[Philip Copeland]

Thanks,

Turned out my Web.xml was screwed up. Shouldn’t I have received an error message from MyEclipse when I deployed. Does MyEclipes validate Web.xml as part of the deployment process?

Phil

[support-michael]

Yes, if you do the following:

1) Enable deployment descriptor validation, see Windows>Preferences>MyEclipse>Editors>XML>Configuration

2) Enable auto-build, see Windows>Preferences>Workbench, “Perform build automatically on resource modification.

[Author]

Posts