Hello,
> I see no reason you would need your servlet to stay in memory. As long
> as it is alive when needed (that is when requests arrive) it's enough.
> Maybe you problem is that it does much than serving request, like
> running background thread, send message to people and so on. Then you
Ex
Hello,
> Please read the other responses to this thread, since they are correct that
> there is no guarantee. However, the current implementation of TC (3.3-6.0)
> will not unload a Servlet unless the entire context is reloaded (with a
> slight exception for JSP pages). But then you are programm
Hello,
> In j2ee specs, there is no provision for unloading an unused servlet.
> Once a servlet has been tarted (load-on-startup or triggered by user
> query), i never get unloaded, unless webapp gets unloaded, which occurs
> at shutdown or during a redeploy (administrative task)
Thanks for qui
