Re: [Wrapper-user] How do I configure JSW for apps with long start and stop times

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

Michael,
    This is the kind of integration that Method 3 was created for.  You 
create a custom
implementation of the WrapperListener interface.   The 
WrapperListener.start method
is called by the Wrapper to launch the application.   It MUST return 
eventually, but it
can take as long as you like to do so.    If it takes longer than the 
value of the
wrapper.startup.timeout property however, the Wrapper will timeout and 
kill the JVM.
The way I suggest doing this is to keep the default timeout value, but call
WrapperManager.signalStarting( 5000 ) every couple seconds to extend the 
startup
timeout.  I suggest this rather than simply setting a long startup 
timeout to make the
Wrapper more responsive if the JVM should hang on startup for any reason.

    Integration Method 3 is a bit more complicated, so be sure to read 
over that section
of the docs along with the javadocs carefully.

Cheers,
Leif

Michael Giroux wrote:
> I am using JSW to launch a Java EE App server as a windows service. 
> When the service is started manually via NET START JONAS, the NET
> START command reports that the service is started, but in fact the App
> server is performing initialization that runs for a few minutes.  From
> an application perspective, the service is not actually started until
> the app server reports that it is started.
>
> Is there any way to configure JSW to delay reporting to Windows that
> the service is started?  For example, can JSW make a call into the
> application to check status and report to Windows that it is started
> only after the application returns some configured value?
>
> Thanks
> Michael Giroux
>