tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <Craig.McClana...@eng.sun.com>
Subject Re: [TC4] ResourcesBase.setCheckInterval() bug
Date Fri, 17 Nov 2000 01:08:44 GMT
Remy Maucherat wrote:

> > You're correct that this kind of code is appropriate (because the
> component
> > has already been started without the thread).
>
> Really ? The threadStart() call is in the start() method, and threadStop()
> is always called in stop(). How would the thread need to be started if the
> component is not started yet ?
>

Consider that you might initialize a resources object with this (among other
stuff):

    resources.setCheckInterval(0);
    resources.start();

and later on, while the container is running, an admin application executes
this:

    resources.setCheckInterval(15);

The thread wasn't started inside resources.start() because the check interval
was zero at that time.  Therefore, it *does* need to be started if
setCheckInterval() is called later.

For long-running servers, we need to remember that configuration is not a
one-time event.  (By the way, IMHO, this is one of the few places where Avalon
doesn't quite "get it".)


>
> Remy

Craig



Mime
View raw message