Re: [Wrapper-user] RE: JVM exit - no log error entries

[Paul C. <cas...@au...>]

Leif,

It's the JVM that is not always outputting a hotspot log when it crashes.
It seems odd that it does sometimes, and not others, when the crash is
produced by following a predefined sequence of events (same each time).

You're right - it's in the JVM.

Regards,

Paul Casanova



|---------+---------------------------------------->
|         |           Leif Mortenson               |
|         |           <le...@ta...>    |
|         |           Sent by:                     |
|         |           wra...@li...|
|         |           ceforge.net                  |
|         |                                        |
|         |                                        |
|         |           22/06/2004 03:53 PM          |
|         |           Please respond to            |
|         |           wrapper-user                 |
|---------+---------------------------------------->
  >--------------------------------------------------------------------------------------------------------------|
  |                                                                                                              |
  |       To:       wra...@li...                                                           |
  |       cc:                                                                                                    |
  |       Subject:  Re: [Wrapper-user] RE: JVM exit - no log error entries                                       |
  >--------------------------------------------------------------------------------------------------------------|




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



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user