Re: [Wrapper-user] How do I prevent wrapper from re-starting after exit ?

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

Elizabeth,
    What version of Java are you using?  Java 1.2 has this problem due 
to its lack of
support for Shutdown hooks, but newer JVMs should all work correctly by 
default
when System.exit is called.

    Could you please rerun your application with the wrapper.debug=true 
property
set and then post the resulting wrapper.log file?
(Trim log entries from previous runs please.)

    Remove the wrapper.on_exit.default and wrapper.single_invocation 
properties.
They are not relevant here.

    In the case of wrapper.on_exit.default, that is already the default 
value.

    The wrapper.single_invocation property is used to make sure that 
more than
one invocation of the same application are never started even if they 
are located
in different directories.  Most applications will fail on startup due to 
port conflicts
etc anyway, but this makes it possible to output a more useful error 
message.

    You are probably looking for the wrapper.max_failed_invocations 
property.
But as I said, that should not be necessary so I would like to see what 
is really
going on.

Cheers,
Leif

Elizabeth Cooper wrote:
> I have tried using
>
> wrapper.on_exit.default=SHUTDOWN
>
> but the wrapper restarts automatically anyway when it receives an exit 
> from the program.
>
> Is there a way to prevent the wrapper from restarting the application 
> when we stop the application using an exit() in the program?
>
> I have searched through all the configuration parameters and I cannot 
> find anything obvious.
>
> Here is some of what my configuration file contains:
>
> wrapper.single_invocation=TRUE
> wrapper.on_exit.default=SHUTDOWN
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>
> wrapper.java.classpath.1=../lib/wrapper.jar
>
> wrapper.java.classpath.2=../Test.jar
> wrapper.java.library.path.1=../lib
>
> wrapper.app.parameter.1=Test
>
> wrapper.ntservice.name=Test
> wrapper.ntservice.starttype=AUTO_START
> wrapper.ntservice.interactive=false