tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4206] New: - missing config files do not cause an error
Date Tue, 16 Oct 2001 18:40:08 GMT
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=4206>.
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=4206

missing config files do not cause an error

           Summary: missing config files do not cause an error
           Product: Tomcat 3
           Version: 3.3 Release Candidate 2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Config
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: doogie@brainfood.com


I'm using a custom deb(really, just a porting of the 3.2 deb to rc2), and, when
doing this porting, I accidentally had /usr/share/tomcat/conf be a directory,
with only a single file(jni_workers.xml).  Tomcat started, but then quit
immediately, without any error.

It's my opinion, that if an application is configured to read a file, and the
file is not there, it should log the problem.  Tomcat does absolutely nothing.

I really wanted to make this bug 'blocking', but I haven't been following tomcat
development, so thought that was going overboard a bit.

doogie2:/etc/tomcat# mv server.xml  server.xml.bak
doogie2:/etc/tomcat# /usr/share/tomcat/bin/tomcat.sh run
Using classpath: /usr/share/tomcat/bin/../lib/tomcat.jar
Using JAVA_HOME: /usr/bin/..
Using TOMCAT_HOME: /usr/share/tomcat/bin/..
EmbededTomcat: Init time 310
EmbededTomcat: Startup time 0
doogie2:/etc/tomcat# ps aux|grep java
root      8447  0.0  0.2  1364  456 pts/2    S    13:32   0:00 grep java

Mime
View raw message