RE: [Wrapper-user] CPU Timeouts and JVM Restarts

[Sal I. <sal...@vo...>]

Messageyou could try this:
wrapper.startup.timeout=0 (def = 30 sec)
wrapper.ping.timeout=0 (def = 30 sec)
wrapper.cpu.timeout=3600 (def = 10 sec)

there are other timeout values.  check out the docs:
http://wrapper.tanukisoftware.org/doc/english/properties.html
  -----Original Message-----
  From: wra...@li...
[mailto:wra...@li...]On Behalf Of
Mi...@bo...
  Sent: Monday, July 26, 2004 12:56 PM
  To: wra...@li...
  Subject: [Wrapper-user] CPU Timeouts and JVM Restarts


  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