wrapper-user

[Wrapper-user] Application Exception handling:How to do it

[Venkatesh S. <Ven...@lc...>]

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please read the disclaimer at the bottom of this e-mail.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Hi All,

My problem,

I have an application that is dependent on multiple resources and there is =
no single entry point/catch-all
class where i can monitor the resources.
I understand that the standard way of handling runtime crashes is to=20

try
{
 // do something
}
catch ( Exception x )
{
 // clear stacks
 WrapperManager.restart();
}
This would allow us to restart the JVM.
My quibble, this is a fairly intrusive way of doing things, as the classes =
now become
WrapperManager dependent.

Has anyone found any other way of doing this ?

I am using Integration method 3.
Any and all suggestions welcome.

Rgds,


**********************************************************************
This email is intended for the named recipient(s) only. Its contents
are  confidential and may only be retained by the named recipient(s)
and may only be copied or  disclosed  with the consent of=20
LCH.Clearnet Limited.   If you are not an intended recipient please
delete this e-mail and notify pos...@lc....

The contents  of this  email are  subject to  contract in all cases,=20
and LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy.  LCH.Clearnet Limited accepts no liability,=20
including liability for negligence, in respect of any statement in=20
this email.

LCH.Clearnet Limited, Registered Office: Aldgate House,=20
33 Aldgate High Street, London EC3N 1EA.    Recognised as a Clearing=20
House under the Financial Services & Markets Act 2000. Reg in England No.25=
932=20
Telephone: +44 20 7426 7000              Internet: http://www.lchclearnet.c=
om
**********************************************************************

Re: [Wrapper-user] Application Exception handling:How to do it

[Leif M. <le...@ta...>]

Venkatesh,
    I agree that littering your code with Wrapper references is not a 
very good idea.
The Wrapper does provide you with a few ways of avoiding this however.

1) Create a shutdown method which centralizes the WrapperManager.restart 
code
to a single location.  (Not much better but it does allow you to make 
your code
cleaner)

2) Register Output triggers with the Wrapper. (v3.0.0 and above)
If your application reliably outputs a message to the console then the 
Wrapper
is able to trigger on that output and shutdown or restart the JVM.   See the
following for details:

http://wrapper.tanukisoftware.org/doc/english/prop-filter-x-n.html

3) Register on-exit events with the Wrapper. (v3.1.0 and above)
The Wrapper is capable of performing different actions depending on the exit
code returned when the JVM exits.   You could for example trigger a restart
if the JVM exits with a non-zero exit code.   See the following for details:

http://wrapper.tanukisoftware.org/doc/english/prop-on-exit-n.html

wrapper.on_exit.default=RESTART
wrapper.on_exit.0=SHUTDOWN

Whenever a fatal error is encountered, simply call System.exit(1) and your
JVM will be restarted by the Wrapper.   About as non-intrusive as you 
can get.

Cheers,
Leif

Venkatesh Sellappa wrote:

>Hi All,
>
>My problem,
>
>I have an application that is dependent on multiple resources and there is no single entry point/catch-all
>class where i can monitor the resources.
>I understand that the standard way of handling runtime crashes is to 
>
>try
>{
> // do something
>}
>catch ( Exception x )
>{
> // clear stacks
> WrapperManager.restart();
>}
>This would allow us to restart the JVM.
>My quibble, this is a fairly intrusive way of doing things, as the classes now become
>WrapperManager dependent.
>
>Has anyone found any other way of doing this ?
>
>I am using Integration method 3.
>Any and all suggestions welcome.
>
>Rgds,
>  
>