|
From: Leif M. <le...@ta...> - 2004-06-22 05:54:35
|
Paul Casanova wrote: >The Wrapper (as always!) was behaving as it should. Strange thing is - >while reproducing exactly the same crash (ie, I've documented the exact >steps to reproduce it), the JVM was inconsistent in generating a hotspot >error log - and hence hotspot error output in the Wrapper log file. Any >timeout values I can tweak to make this more consistent? > > The JVM process is crashing here, so the only possible timeout that could have any effect might be the wrapper.ping.timeout. In this case I doubt that it would be useful however as the Wrapper is detecting that the JVM process is gone long before the timeout. When you say inconsistent, what do you mean? If the JVM is simply not always dumping out a HotSpot error, then that is internal to the JVM and is most likely a timing issue. If the Wrapper is somehow clipping some of the output from the JVM then that may be something that I need to work on. I know there used to be a problem with this when the dump stack trace on failed exit feature was enabled. >I'll have to search the bug database to see if this is a new bug. I've >found some similar, but I need to investigate more thoroughly - when I have >time. > > I know how that goes. Good luck Leif |