[offtopic] Opinion - Error messages
I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3621) 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:512) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [offtopic] Opinion - Error messages
Is this a request for help, or just a rant? Please let us know. John -Original Message- From: Jim Henderson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: [offtopic] Opinion - Error messages I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext. java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext .java:3621) 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.j ava:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [offtopic] Opinion - Error messages
Jim Henderson wrote: I have been in IT for approximately 25 years Scary ;-) and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. No Lisp? That's the problem! I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. You deverse an F also for the kind of information you just posted ;-) Please tell us more what you are trying to do. Which platform?, Which Tomcat version (I guess its 4.1.x...but I don't like guessing), What your app is trying to do and most importantly, add your web.xml file. Is the Tomcat example working? Have you try to increase the logging level? Then we will revise your note and maybe help you and give a C ;-) -- Jeanfrancois ---see--- (http://jakarta.apache.org/site/mail.html) :-) Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3621) 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:512) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [offtopic] Opinion - Error messages
I take help! :) (I am just frustrated and the post was intended to be positive criticism.) My app works just fine (minus the mail function) IF I do not add my Context info to server.xml. My context data is larger (includes Valve, Logger, Resource, ResourceParms, and Environment items) but I have trimmed it down to the following that is inserted in the 4.1.18 distribution after the examples context and before /Host. And it is strange, if I run the app then add the server.xml entry without clearing the work subdirectory and without redeploying, the error does not occur. This was a very confusing issue, it seemed to work sometimes and sometimes not. But if I add my Context tag to the server.xml, then deploy am WAR file, the error occurs. It is the following trimmed Context that caused the error. Context path=/mfnettags docBase=mfnettags reloadable=false debug=5 swallowOutput=false useNaming=true /Context Thanks! -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 10:08 AM To: 'Tomcat Users List' Subject: RE: [offtopic] Opinion - Error messages Is this a request for help, or just a rant? Please let us know. John -Original Message- From: Jim Henderson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: [offtopic] Opinion - Error messages I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext. java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext .java:3621) 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.j ava:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands
