[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange tomcat behavior

To: ajug-members@ajug.org
Subject: Re: Strange tomcat behavior
From: Jerzy Puchala <jerzypuc@scdi.com>
Date: Fri, 8 Nov 2002 11:41:36 -0500 (EST)
In-Reply-To: <20021108163200.6153.qmail@web11402.mail.yahoo.com>
Try to look  into the DTD for the mentioned configuration files. They 
are sensitive for the order of the node elements. Maybe this will 
help.

Jerzy

On Fri, 8 Nov 2002, Matthew Phillips wrote:

> It looks like a problem in the tomcat.conf file or the
> web.xml file.  I had a similar problem when I had an
> error in my tomcat.conf file, but I don't remember
> exactly what it was.
> 
> Matthew Phillips
> 
> --- "Jason R. Kretzer" <jason@OpinionOne.com> wrote:
> > Hello all,
> > 
> > I am using Tomcat 4.1.12, Java 1.4.1, and Apache
> > 1.3.26.  Whenever I 
> > start up the Tomcat, it starts fine but as soon as
> > one of the servlets 
> > is accessed, it throws Exception 1 below in the
> > catalina.out.  Anyone 
> > know which document this error is being thrown in
> > regards to?
> > 
> > Secondly, I have one context with three subfolders. 
> > /Context/subfolder1 
> > , /Context/subfolder2, /Context/subfolder3. 
> > subfolders1 and 3 show up 
> > fine but when I access subfolder2, an exception
> > displays on the screen 
> > that the resource is not avaiable.  I have them
> > listed in httpd.conf 
> > correctly, of this I am sure.
> > 
> > The only clue I have as to why subfolder2 is not
> > available, is when 
> > Tomcat is shut down and Exception 2 below is added
> > to the catalina.out.
> > 
> > Any suggestions would be appreciated.
> > 
> > -Jason
> > 
> > Exception 1
> >
> ============================================================================
> >
> ============================================================================
> > Starting service Tomcat-Apache
> > Apache Tomcat/4.1.12
> > Nov 8, 2002 9:46:43 AM
> > org.apache.commons.digester.Digester fatalError
> > SEVERE: Parse Fatal Error at line 254 column 4: The
> > markup in the 
> > document following the root element must be
> > well-formed.
> > org.xml.sax.SAXParseException: The markup in the
> > document following the 
> > root element must be well-formed.
> >     at 
> >
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232)
> >     at 
> >
> org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:213)
> >     at 
> >
> org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:366)
> >     at 
> >
> org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296)
> >     at 
> >
> org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1269)
> >     at 
> >
> org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(XMLDocumentScannerImpl.java:1032)
> >     at 
> >
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
> >     at 
> >
> org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> >     at 
> >
> org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> >     at
> >
> org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> >     at 
> >
> org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
> >     at
> >
> org.apache.commons.digester.Digester.parse(Digester.java:1495)
> >     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:3493)
> >     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:579)
> >     at 
> >
> org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:257)
> >     at
> >
> org.apache.catalina.core.StandardHost.install(StandardHost.java:772)
> >     at 
> >
> org.apache.catalina.connector.warp.WarpConfigurationHandler.deploy(Unknown
> > 
> > Source)
> >     at 
> >
> org.apache.catalina.connector.warp.WarpConfigurationHandler.handle(Unknown
> > 
> > Source)
> >     at
> >
> org.apache.catalina.connector.warp.WarpConnection.run(Unknown
> > Source)
> >     at java.lang.Thread.run(Thread.java:536)
> >
> ============================================================================
> >
> ============================================================================
> > 
> > 
> > 
> > Exception 2
> >
> ============================================================================
> >
> ============================================================================
> > 
> > Stopping service Tomcat-Standalone
> > Stopping service Tomcat-Apache
> > Catalina.stop: LifecycleException:  Container 
> > StandardContext[/DataManager/QTField] has not been
> > started
> > LifecycleException:  Container
> > StandardContext[/DataManager/QTField] has 
> > not been started
> >     at 
> >
> org.apache.catalina.core.StandardContext.stop(StandardContext.java:3569)
> >     at
> >
> org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
> >     at
> >
> org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
> >     at 
> >
> org.apache.catalina.core.StandardService.stop(StandardService.java:554)
> >     at 
> >
> org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
> >     at
> >
> org.apache.catalina.startup.Catalina.start(Catalina.java:541)
> >     at
> >
> org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
> >     at
> >
> org.apache.catalina.startup.Catalina.process(Catalina.java:180)
> >     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:324)
> >     at
> >
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
> >
> ============================================================================
> >
> ============================================================================
> > 
> > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> U2 on LAUNCH - Exclusive greatest hits videos
> http://launch.yahoo.com/u2
> 

-- 
+--------------------------------+
|         Jerzy Puchala          |
+--------------------------------+
|       jerzypuc@scdi.com        |
+--------------------------------+
References:
- Re: Strange tomcat behavior
  - From: Matthew Phillips <matthew_a_phillips@yahoo.com>
Prev by Date: Re: Strange tomcat behavior
Next by Date: Layout Managers
Prev by thread: Re: Strange tomcat behavior
Next by thread: Layout Managers
Index(es):
- Date
- Thread