System.exit() brings down Jetty/Cocoon

[Litrik De Roy]

A call to System.exit(0) (for example in an XSP page) brings down 
Jetty/Cocoon without any warning or error message.

Is Jetty/Cocoon supposed to behave this way?

How can this be prevented?

PS: Yes I know that calling System.exit() is stupid, but our 
Cocoon-based webapp is crashing intermittingly without any trace and I'm 
suspecting that somewhere in one of the 25 third-party jars a 
System.exit() gets called (for whatever reason). Hence my testing, and 
this question.

--

Litrik De Roy
www.litrik.com