Re: [Wrapper-user] Wrapper notification...

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

Luis,

>Ahh yes.. Cross platform unity is the issue at hand.  And as you said,
>the ability to execute is exactly what I'm thinking of.
>  
>
It is not always possible to make everything 100% cross platform.   The 
NT properties
and related features are a good example.  But I always try where it 
makes sense.  It
just makes it than much easier for user who are trying to support 
multiple platforms.

>We already have notifications when there are additions to the
>environment, but we actually don't allow the JVM to restart on all but
>the JMS server.  We prefer at the moment, to analize the situation and
>find the cause of jvm to fail.  So we set the max_failed_invocations =1.
>So then the service terminates.  I should have included this in my
>initial email.  It probably would have made more sense of my message
>when I ask whether or not the wrapper service termination would be a
>considered a service failure.
>  
>
In that case, it might actually work for you.  I have never used the NT 
recovery features,
so this may not help.  But the Wrapper will always exit with an exit 
code of 1 if there
were any problems.  It exits with code 0 if the shutdown was normal.

Problem is that I just looked at the code and the Wrapper is not exiting 
with an error exit
code in this case.

Let me know what you will need on exit to make it useful for you.  It 
looks like I will have
to go through and make sure that cases like this always result in an 
error exit code.

Currently, the exit codes appear to be correct if there are any problems 
while starting up.

Cheers,
Leif