our Resin-Pro 3.0.22 deploy is experiencing 'silent' JVM exits.  with a bit of 
code tweaking on our side, we managed to capture the following stack trace:

        at java.lang.Runtime.halt(Runtime.java:252)
         at com.caucho.server.admin.PingThread.run(PingThread.java:361)
         at java.lang.Thread.run(Thread.java:595)

we have not enabled ping in resin.conf.

should PingThread be doing this?  or might this be a bug?
Register today for the Algorithmics Risk Conference 2007, September 24 - 26, 
Cannes, France.

This email and any files transmitted with it are confidential and proprietary 
to Algorithmics Incorporated and its affiliates ("Algorithmics"). If received 
in error, use is prohibited. Please destroy, and notify sender. Sender does not 
waive confidentiality or privilege. Internet communications cannot be 
guaranteed to be timely, secure, error or virus-free. Algorithmics does not 
accept liability for any errors or omissions. Any commitment intended to bind 
Algorithmics must be reduced to writing and signed by an authorized signatory.

resin-interest mailing list

Reply via email to