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)
Kamil Burzynski a écrit :
Hello,
I would like to create one of my servlets to be 'sticky': to be sure
that Tomcat will never try to remove this servlet from memory.
Is <load-on-startup> enough? I know that it will start my servlet as
soon as tomcat starts, but will tomcat ever try to remove such servlet?
E.g. if there will be 1 month of inactivity, or so much requests arrive
that out-of-memory will happen?
Maybe I should create some background thread or socket or whatever?
Any solutions appreciated, thanks in advance.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
