Archives! (was Re: SV: tomcat 4.1.12 just stopped working, help !)
Hmm, I just got enlisted on this mailinglist so I don$B%((Bt have yesterdays mail (Bfrom it. Is there an archive from yesterday, or maybe you could mail me the thread ? (B (B(Ouch. That's a long line.) (B (BArchives: (B (Bhttp://jakarta.apache.org/site/mail.html (B (BAnd after you read the policies on this page, there's a link at the (Bbottom of the page that takes you to a page with, among other things, (Bseveral archive services listed on it. You really should have seen this (Bpage when you signed up, by the way. (B (BI like marc, for no particular reason: (B (Bhttp://marc.theaimsgroup.com/(general list) (Bhttp://marc.theaimsgroup.com/?l=tomcat-userr=1w=2 (tomcat-user) (B (B-- (BJoel Rees [EMAIL PROTECTED] (B (B (B-- (BTo unsubscribe, e-mail: mailto:[EMAIL PROTECTED] (BFor additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat 4.1.12 just stopped working, help !
Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445) 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.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) 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) Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 120 column 15: The content of element type servlet must match
Re: tomcat 4.1.12 just stopped working, help !
Hmm, it looks like an error in the web.xml of a certain app. Did you by any chance change the web.xml of any of your web applications ? [EMAIL PROTECTED] wrote: Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445) 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.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) 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) Jan 7, 2003 9:47:29 AM
SV: tomcat 4.1.12 just stopped working, help !
Hehe, not that I know of ;)) Well there is a web.xml in .../conf/ and additional web.xml in every catalog in .../webapps/ so is there any good way of finding out in which the error occurs ? -Ursprungligt meddelande- Från: Peng Tuck Kwok [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 09:54 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hmm, it looks like an error in the web.xml of a certain app. Did you by any chance change the web.xml of any of your web applications ? [EMAIL PROTECTED] wrote: Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445) 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.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400
Re: tomcat 4.1.12 just stopped working, help !
Whats about using a tool like XML Spy. With this one you can check, if the web.xml files are well formed and valid. Valid means, that they match the rules defined in the web-app_2_3.dtd, which seems to be the problem in that case. HTH Holger - Original Message - From: Peng Tuck Kwok [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 9:53 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! Hmm, it looks like an error in the web.xml of a certain app. Did you by any chance change the web.xml of any of your web applications ? [EMAIL PROTECTED] wrote: Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17 3) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36 2) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29 6) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator. java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8 78) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo cumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1445) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume ntFragmentScannerImpl.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:116 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja va: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(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start
SV: tomcat 4.1.12 just stopped working, help !
I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17 3) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36 2) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29 6) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator. java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8 78) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo cumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1445
Re: SV: tomcat 4.1.12 just stopped working, help !
If you are sure that is the xml in question, can you forward it to the list so we can have a look? [EMAIL PROTECTED] wrote: I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17 3) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36 2) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29 6) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator. java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8 78) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo cumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:987
RE: tomcat 4.1.12 just stopped working, help !
Or use cooktop if you don't have XML Spy Cheers Kevin -Original Message- From: Holger Brozio [mailto:[EMAIL PROTECTED]] Sent: 07 January 2003 09:14 To: Tomcat Users List Subject: Re: tomcat 4.1.12 just stopped working, help ! Whats about using a tool like XML Spy. With this one you can check, if the web.xml files are well formed and valid. Valid means, that they match the rules defined in the web-app_2_3.dtd, which seems to be the problem in that case. HTH Holger - Original Message - From: Peng Tuck Kwok [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 9:53 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! Hmm, it looks like an error in the web.xml of a certain app. Did you by any chance change the web.xml of any of your web applications ? [EMAIL PROTECTED] wrote: Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17 3) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36 2) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29 6) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator. java:1953) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8 78) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo cumentFragmentScannerImpl.java:1144) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:987) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1445) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume ntFragmentScannerImpl.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:116 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja va: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(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347
Re: tomcat 4.1.12 just stopped working, help !
You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17 3) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36 2) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29 6) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator. java:1953
Re: tomcat 4.1.12 just stopped working, help !
Hi, I had similar problem but not exactly the same. Please refer to my yesterdays mail for a possible solution.. regards, Keshav - Original Message - From: Manavendra Gupta [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 5:32 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). org.xml.sax.SAXParseException: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException
SV: tomcat 4.1.12 just stopped working, help !
Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail from it. Is there an archive from yesterday, or maybe you could mail me the thread ? /D -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:21 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi, I had similar problem but not exactly the same. Please refer to my yesterdays mail for a possible solution.. regards, Keshav - Original Message - From: Manavendra Gupta [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 5:32 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error SEVERE: Parse Error at line 114 column 15: The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t
Re: tomcat 4.1.12 just stopped working, help !
Hi Search in archive with text - Parse error in application web.xml regards, keshav - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 4:52 PM Subject: SV: tomcat 4.1.12 just stopped working, help ! Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail from it. Is there an archive from yesterday, or maybe you could mail me the thread ? /D -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:21 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi, I had similar problem but not exactly the same. Please refer to my yesterdays mail for a possible solution.. regards, Keshav - Original Message - From: Manavendra Gupta [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 5:32 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Starting service Tomcat-Standalone Apache
SV: tomcat 4.1.12 just stopped working, help !
The archive only covers from June 5, 2000 to March 13, 2002 :(( (unless you know of another archive than: http://mikal.org/interests/java/tomcat/ ) So, can someone tell me how I am supposed to get a hold of the Parse error in application web.xml thread ? ;) /Dan -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:46 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi Search in archive with text - Parse error in application web.xml regards, keshav - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 4:52 PM Subject: SV: tomcat 4.1.12 just stopped working, help ! Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail from it. Is there an archive from yesterday, or maybe you could mail me the thread ? /D -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:21 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi, I had similar problem but not exactly the same. Please refer to my yesterdays mail for a possible solution.. regards, Keshav - Original Message - From: Manavendra Gupta [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 5:32 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp openajp13 8080/tcp openhttp-proxy So evidently something happens ;) But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead. If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone. But if I directly run .../bin/catalina.sh run I get this: (if someone can get any clue from this) [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR
Re: tomcat 4.1.12 just stopped working, help !
Hi, This is the copy of the text I mailed yesterday- Thanks for the reply. I had same exception thrown even with fresh installation of tomcat 4.1.18 without my application included in webapps. Anyway I solved this problem by uninstalling tomcat, removing all classpath settings from environmental variables and installing tomcat again. Now it is working fine, any way this will remain puzzle to me as no one has reported similar bug anywhere else !! - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 5:43 PM Subject: SV: tomcat 4.1.12 just stopped working, help ! The archive only covers from June 5, 2000 to March 13, 2002 :(( (unless you know of another archive than: http://mikal.org/interests/java/tomcat/ ) So, can someone tell me how I am supposed to get a hold of the Parse error in application web.xml thread ? ;) /Dan -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:46 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi Search in archive with text - Parse error in application web.xml regards, keshav - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 4:52 PM Subject: SV: tomcat 4.1.12 just stopped working, help ! Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail from it. Is there an archive from yesterday, or maybe you could mail me the thread ? /D -Ursprungligt meddelande- Från: Keshava Murthy [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 12:21 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! Hi, I had similar problem but not exactly the same. Please refer to my yesterdays mail for a possible solution.. regards, Keshav - Original Message - From: Manavendra Gupta [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 5:32 AM Subject: Re: tomcat 4.1.12 just stopped working, help ! You said your tomcat stopped working somewhere around christmas. What were the last servlets you deployed and in what contexts? Or is that /examples is the only context that you have? ~manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 1:18 AM Subject: SV: tomcat 4.1.12 just stopped working, help ! I checked the .../webapps/examples/WEB-INF/web.xml and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run .../bin/catalina.sh run I get this: [root@star bin]# ./catalina.sh run Using CATALINA_BASE: /etc/jakarta-tomcat-4.1.12 Using CATALINA_HOME: /etc/jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp Using JAVA_HOME: /usr/java/j2sdk1.4.1 Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=6/291 config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties I still don´t get any answer from port 8080 :(( /Dan -Ursprungligt meddelande- Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]] Skickat: den 7 januari 2003 23:42 Till: Tomcat Users List Ämne: Re: tomcat 4.1.12 just stopped working, help ! As the log suggests, the deployment descriptor of the servlet does not conform to the DTD : The content of element type servlet must match (icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini t-param*,load-on-startup?,run-as?,security-role-ref*). Check the web.xml file for the last few servlets you deployed. The descriptor elements should occur in the same order as mentioned above. ~Manav. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 12:44 AM Subject: tomcat 4.1.12 just stopped working, help ! Hi all Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue. This is what I know: If I start tomcat with .../bin/startup.sh and then run a portscan I can see: 8009/tcp
