You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/10/04 21:12:26 UTC

DO NOT REPLY [Bug 13309] New: - Catalina calls System.exit()

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()

           Summary: Catalina calls System.exit()
           Product: Tomcat 4
           Version: 4.1.10
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: justin@somanetworks.com


Catalina calls System.exit()from several locations:
  -- core/StandardServer calls it
  -- several classes in startup call it

This makes life difficult for application developers who wish to embedd Tomcat
into their application, such as to attach a web interface to an application
which is otherwise not a web application.

In particular it may not be a critical failure if tomcat fails to start up
successfully, except that Catalina calls System.exit. It may also be a
recoverable error, as the containing system could try re-starting it with
different arguments. 

Please note that the documentation for CatalinaService at least in part implies
that it is expected to be used in this fashion: "designed to allow easier
wrapping by system level components".

So, I think Catalina should not call System.exit(), or should only call
System.exit() from a loader which is not intended to be wrapped by a system
level component.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>