Hi, The servlet container is free to destroy and reinitialize servlets, including load-on-startup servlets. Tomcat doesn't normally do this, however.
Could it be you had enough usage to run our of memory, thereby forcing an aggressive GC? If you're running with verbose:gc, you'd see an Unloading [class name of your servlet] message in your console log. Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Matt Jackson [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 09, 2003 10:07 AM >To: 'Tomcat Users List' >Subject: Unexpected reload of MainServlet > >In the middle of a fairly busy day in terms of site activity, our >MainServlet was destroyed and reinitialised unexpectedly. We have not >experienced any other strange Tomcat behaviour almost a year of continuous >use and this is our first 'glitch'. We are using Tomcat 3.2.4 on Suse 7.1. > >Does anyone have any pointers as to why this may happen? > >TIA > >Matt > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
