DO NOT REPLY [Bug 4023] New: - exceptions that terminate engine should be saved in a log

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4023>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4023

exceptions that terminate engine should be saved in a log

           Summary: exceptions that terminate engine should be saved in a
                    log
           Product: Tomcat 4
           Version: 4.0.1 Beta 1
          Platform: PC
        OS/Version: Windows 9x
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pogo_tomcat@yahoo.com


When debugging Tomcat configuration problems, it would be very helpful if
exceptions that caused Tomcat to terminate were saved to a log file rather than
just being echoed to stdout/err.  On Windows, it is hard sometimes to get useful
information from console output, because it's always closing when you don't want
it to or scrolling up past the buffer.

In general, though, it seems like good policy for any engine-killing event to be
recorded in the official log files.

Here's an example of an exception which does not go to the logs.  This is from a
misconfigured context directory in server.xml.

java.lang.IllegalArgumentException: Document base c:\views\docs does not
exist or is not a readable directory
        at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.
java:182)
        at org.apache.catalina.core.StandardContext.setResources(StandardContext
.java:1075)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3
271)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)

        at org.apache.catalina.core.StandardHost.start(StandardHost.java:612)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)

        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:307
)
        at org.apache.catalina.core.StandardService.start(StandardService.java:3
88)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:505
)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:776)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)

Seen with Tomcat 4.0.1b1, but I believe the problem is in base 4.0 as well.