[Wrapper-user] Another Fatal error in Wrapper

[Heather L. <hea...@th...>]

Leif,

Hi.  Thank you for your quick response and fix of the wrapper defect in
3.2.0 and 3.2.1.  Unfortunately, I've had another wrapper crash.  This
one was on a different (but similar) system (Windows, wrapper version
3.2.0).

FATAL  | wrapper  | 2006/10/11 15:11:21 | encountered a fatal error in
Wrapper
FATAL  | wrapper  | 2006/10/11 15:11:21 |   exceptionCode    =3D
EXCEPTION_ACCESS_VIOLATION
FATAL  | wrapper  | 2006/10/11 15:11:21 |   exceptionFlag    =3D
EXCEPTION_NONCONTINUABLE_EXCEPTION
FATAL  | wrapper  | 2006/10/11 15:11:21 |   exceptionAddress =3D =
7C82F527
FATAL  | wrapper  | 2006/10/11 15:11:21 |   Read access exception from
0061FEBD
FATAL  | wrapper  | 2006/10/11 15:11:21 | <-- Wrapper Stopping due to
error in service control handler.
   =20
Thanks,
Heather


-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Tuesday, October 10, 2006 11:20 AM
To: wra...@li...
Subject: Re: [Wrapper-user] Fatal error in Wrapper

Heather,
Another user just reported a similar problem.  They seem to be able to
reproduce it more easily.  I have requested more information.  But you
might want to monitor the following bug issue.
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D425187&aid=3D157453=
7&gro
up_id=3D39428

Cheers,
Leif

Heather Leonard wrote:
> Leif,
>
> Version: 3.2.0
> Platform: Windows Server 2003
>
> I have verified that wrapper.jar, wrapper.exe and wrapper.dll are all=20
> from the same version.
>
> The error occurred at least 11 days after the JVM was launched so=20
> definitely not at start up.  After the crash was discovered, the=20
> service was restarted without error (a couple of days later). =20
> Unfortunately, I have been unable to reproduce the error.  Since it=20
> occurred in customer's production system, I have copied their=20
> installation on my machine to try to reproduce the error.  In this=20
> way, I can reproduce the exact conditions when the error occurred. =20
> However, it is not exactly the same system.  Since the application=20
> receives data over a socket, is it possible for the client to send=20
> something that would cause this error?
>
> Thanks,
> Heather
>
> -----Original Message-----
> From: wra...@li...
> [mailto:wra...@li...] On Behalf Of Leif=20
> Mortenson
> Sent: Thursday, October 05, 2006 11:05 AM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Fatal error in Wrapper
>
> Heather,
>     You somehow figured out a way to crash the Wrapper process itself.

> Unfortunately,
> this is a state that the Wrapper is not able to recover from on its
own.
> I would definitely like to figure out a way to reproduce this as this=20
> is the first I have heard of this problem.
>
>     Could you tell me what version of the Wrapper you are using as=20
> well as the platform.
> Are you sure that you are using the wrapper.jar, wrapper.exe, and=20
> wrapper.dll all from the same version?
>
>     The message about packet type 110 is perplexing.  Packet Id #110=20
> is the access key.
> I double checked the code, but this is only sent from the JVM to the=20
> Wrapper process
> and then only once at startup.   Your error log shows that this packet

> Id 110 was
> received by the JVM from the Wrapper.
>
>     How long after the JVM was launched did you encounter this error?
>
> Cheers,
> Leif
>
> Heather Leonard wrote:
>  =20
>> Hi,
>>
>> My application crashed and the following error was in the wrapper
log.
>>
>> INFO   | jvm 1    | 2006/09/29 18:46:20 | Wrapper code received an=20
>> unknown packet type: 110
>> FATAL  | wrapper  | 2006/09/29 18:46:25 | encountered a fatal error=20
>> in
>>    =20
>
>  =20
>> Wrapper
>> FATAL  | wrapper  | 2006/09/29 18:46:25 |   exceptionCode    =3D=20
>> EXCEPTION_ACCESS_VIOLATION
>> FATAL  | wrapper  | 2006/09/29 18:46:25 |   exceptionFlag    =3D=20
>> EXCEPTION_NONCONTINUABLE_EXCEPTION
>> FATAL  | wrapper  | 2006/09/29 18:46:25 |   exceptionAddress =3D
>>    =20
> 7C82F527
>  =20
>> FATAL  | wrapper  | 2006/09/29 18:46:25 |   Read access exception
from
>>    =20
>
>  =20
>> 0061FE7D
>> FATAL  | wrapper  | 2006/09/29 18:46:25 | <-- Wrapper Stopping due to

>> error in service main.
>>
>> I have since been unable to reproduce the crash.  I have two=20
>> questions.  Can anyone explain this error and why it would occur?
>> Also, I would like the application to restart when an error like this

>> occurs.  Will setting the wrapper.on_exit.default property to RESTART

>> cause a restart in this case?
>>
>> Thanks,
>> Heather Leonard
>>