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=13309>. 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=13309 Catalina calls System.exit() [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-04 22:06 ------- Using BootstrapService does not avoid the problem. BootstrapService simply wraps around CatalinaService and Catalina itself. Since Catalina.java contains calls to System.exit(), it can still happen even if you use BootstrapService. Calling System.exit() in response to an exception, no matter how unlikely the exception, makes it dangerous to embedd Catalina into a larger system. Instead of calling System.exit() in response to an exception, Catalina.java (and other locations) should propagate an exception to the calling class, deferring the decision to terminate the JVM as much as possible. Ideally you should only call System.exit() from a main() method, as a means of ensuring that all threads terminate--and it would still be nice to interrupt all the running threads, and invoke any shutdown hooks, prior to killing the JVM. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
