tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk" <mt...@mappingsoft.com>
Subject RE: Jk2 shutdown
Date Mon, 01 Jul 2002 18:30:51 GMT


> -----Original Message-----
> From: costinm@covalent.net [mailto:costinm@covalent.net] 
> Sent: 1. srpanj 2002 19:40
> To: Tomcat Developers List
> Subject: Re: Jk2 shutdown
> 
> 
> On Mon, 1 Jul 2002, Mladen Turk wrote:
> 
> We already have a mechanism/API for shutdown - and I don't 
> see any good reason to add another one for the JNI call. The 
> fewer 'special' APIs we have for JNI, the better it is for 
> maintainance.
>

Yes, but It doesn't work, at least I wasn't been able to invoke it.
And it isn't API, it just calls the TomcatStarter with the stop param,
and the change of ARG init param, enables that 'stop' to be customizable
(if its gonna be changed someday).

> What I would do is just use the existing ajp13 shutdown. If 
> there's anything the TomcatStarter must do on shutdown, we 
> can add another  hook (== coyote ActionCode ) for shutdown, 
> but use the normal callback mechansim from JNI ( with the 
> ajp13 shutdown message ).
>

We still need to destroy the jvm on shutdown, and since we are using the
TomcatStarter for starting I'm pretty much in favor for using it for
shutdown too, cause that's our application entry point when used
inprocess.
If something else provoke the shutdown then we'll need another callback
or jkSetAttribute, to signal the jni worker to destroy the jvm.


MT.


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message