|
From: <Mi...@bo...> - 2004-07-26 19:55:52
|
I'm currently using v3.1.0 of the wrapper, and I haven't had too many problems with it. However, I am now running into a problem where the wrapper thinks that my JVM has hung and does an automatic restart. I get "Wrapper Process has not received any CPU time for 38 seconds. Extending timeouts." and immediately following that I get a JVM restart. My service is running on machines that experience heavy load, and my service itself is a fairly large multi-threaded application that will produce its own heavy load. I would rather attempt to "ignore" the whole CPU/Ping etc. timeout values because I don't want my JVM to be automatically restarted. What is the best way to set all of the timeout/interval configuration parameters so that I can ignore these checks, and deal with the consequences of a "hung" JVM with a manual intervention? Thanks, Mitch |