Re: [Wrapper-user] wrapping catalina

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

David Resnick wrote:

>1. When shutting down a wrapper service using "net stop XXX" from the
>command line, the command gives up ("service cannot be stopped") before
>the wrapper.shutdown.timeout time has been reached. Is this a problem
>with the net command? Does anyone know of a solution to this?
>
What version of the Wrapper are you using?  From the reference to Silver 
Egg, it is
probably fairly old.  I transferred the license back to my own private 
domain several
months ago.

Newer versions have added the wrapper.jvm_exit.timeout
property to control the amount of time to allow the JVM to exit after the
WrapperManager has called System.exit().  This interval can take a few 
minutes
if the user code has implemented any shutdown hooks which do not return
immediately.

Take a look at the following URL for further details:
http://wrapper.tanukisoftware.org/doc/english/prop-jvm-exit-timeout.html

Also, I would suggest reviewing the integration methods as one of the 
examples
is for integrating with Tomcat.  It might have some new info not 
available in the
version you were using.
http://wrapper.tanukisoftware.org/doc/english/integrate.html

>2. I have wrapped tomcat which includes a number of web applications. As
>far as I'm concerned, tomcat is not started until these web applications
>have completed their initialization. The problem is that tomcat doesn't
>work that way, and instead signals that it is started as soon as it can
>start the various web apps. Does someone have a way of making the
>wrapper service start operation continue until a number of web apps have
>initialized first?
>
Take a look at the 3 integration methods,  If you need fine control over
exactly when the WrapperManager returns that the application has actually
started then you are going to need to use method 3 and implement your
own class than implements WrapperListener.

Please post the solution you come up with as it may be useful to other
users.

Cheers,
Leif