Re: [Wrapper-user] JVM can't restart

[<a.s...@aa...>]

Hi Chuck,

thanks, will give it a try.

I already had the outofmemory filter in place. Thanks anyway.

Andr=E9

Chuck Williams schrieb:
> Hi Andre,
>
> I had this same problem and worked around it with these additional
> config keys:
>
>  =20
>> # Restart on all but normal exits (also works around problem where
>> wrapper.restart.delay ignored on jvm halts like SIGSEGV)
>> wrapper.on_exit.default=3DRESTART
>> wrapper.on_exit.0=3DSHUTDOWN
>>
>>    =20
>
> With this config, the first restart attempt (which ignores
> wrapper.restart.delay) will still fail, but that failure will cause a
> second restart attempt that will honor the delay and thus succeed.
>
> You might also find this useful:
>
>  =20
>> # Restart on OOM
>> wrapper.filter.tigger.1=3Djava.lang.OutOfMemoryError
>> wrapper.filter.action.1=3DRESTART
>>
>>    =20
>
> Chuck
>
>
> Andr=E9 Schild wrote on 11/21/2006 07:44 AM:
>  =20
>> Hello,
>>
>> we are using the service wrapper with good success.
>> But we have one thing who troubles it a bit.
>>
>> Sometimes when a JVM is killed due to out of memory errors, the JVM is=
=20
>> not restarted.
>> But most of the time it restarts just fine.
>>
>> In the logfile we see this:
>>
>> ERROR  | wrapper  | 2006/11/21 15:11:33 | JVM appears hung: Timed out=20
>> waiting for signal from JVM.
>> STATUS | wrapper  | 2006/11/21 15:11:33 | Dumping JVM state.
>> ERROR  | wrapper  | 2006/11/21 15:11:38 | JVM did not exit on request,=
=20
>> terminated
>> STATUS | wrapper  | 2006/11/21 15:11:38 | JVM exited in response to=20
>> signal SIGKILL (9).
>> ERROR  | wrapper  | 2006/11/21 15:11:38 | Unable to start a JVM
>> STATUS | wrapper  | 2006/11/21 15:11:38 | <-- Wrapper Stopped
>>
>> In the wrapper config we have these parameters:
>>
>> wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE
>> wrapper.restart.delay=3D15
>> wrapper.restart.reload_configuration=3DTRUE
>>
>>
>> What seems strange is the fact that between the "JVM exited in respons=
e=20
>> to signal SIGKILL (9)." and the "Unable to start a JVM" there is no 15=
=20
>> second delay. The one configured as restart.delay.
>>
>> So we assume that the new JVM can't instaltly restart, because the old=
=20
>> one is not completely shutdown yet.
>>
>> After such a error condition we can just restart it without any proble=
ms.
>>
>> Andr=E9
>>
>>
>> ----------------------------------------------------------------------=
---
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to shar=
e your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>  =20
>>    =20
>
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
 your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>  =20