>Just discovered that if my servlet calls System.exit() I get the
>expectedresult - the currently running JVM is shut down.
>Of course this means that the webserver, which is sharing it's JVM
>with the servlet is also shutdown.
>Although this behaviour is exactly as expected from the
>documentation, I am a little surprised that it would be so easy to
>kill a server. I'm interested to hear what other people think about
>this.
system.exit() is a nasty thing to do in servlets. Also, thats where
the "out-of-box" architectures of JRun et al. come handy. Being a
seperate process (and VM) than the server itself - its easy to start
/ stop it independently of the server process. Not just System.exit()
call but a 'crash', too, will not bring down the entire server in
this architecture.
_s_
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
