[Wrapper-user] RE: Disabling JVM ping

[Clement, N. <ncl...@qv...>]

Leif,

Thanks for your quick reply!  The application was trying to output about 9MB
worth of log data at the time (something we're obviously going to try and
reduce).  I have installed the 3.0.1 version of wrapper and have not seen
the problem since.  I will monitor it closely over the coming days and let
you know if the problem re-occurs.

My original question still stands - I'm uncomfortable with the idea of the
application being restarted automatically.  I'd rather our support people
have to restart the application manually in the rare event of a JVM hang.
Would it be possible to disable pinging completely as an option for advanced
users?  Just a suggestion of course.

Thanks very much for your prompt assistance!

Nathan


From: Leif Mortenson <leif@ta...> 
 Re: Disabling JVM ping   
2003-04-01 04:22  
 Nathan,
     Does your application output large amounts of output to the console? 
  There was bug
 that would cause the native side of the Wrapper to spend too much time 
 processing
 input from the JVM and forget about doing its other jobs.  This was 
 causing timeouts
 like you mentioned below.   It actually had nothing to do with pinging 
 that is why
 changing the ping timeout had no effect for you.
     I fixed this in 3.0.1 that was just released a couple days ago. 
  Could you please give
 that version a try and get back to me about whether or not it fixes your 
 problem.
     Be sure to return any modified timeouts to their default values.
     Also note that there were some changes with the scripts and config 
 file in the 3.0.0
 release.  You should no longer set the pid in the wrapper conf file.  It 
 is now handled
 from within the shell scripts.  This was done to reduce the number of 
 things that a
 user has to modify.
 
 Cheers,
 Leif