Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 50826 invoked from network); 9 Jan 2003 18:43:42 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 Jan 2003 18:43:42 -0000 Received: (qmail 23758 invoked by uid 97); 9 Jan 2003 18:44:25 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 23688 invoked by uid 97); 9 Jan 2003 18:44:24 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 23649 invoked by uid 98); 9 Jan 2003 18:44:23 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <912813B4551CD511983700D0B7696A8F90EB10@EXCHANGE> From: Matt Jackson To: 'Tomcat Users List' Subject: RE: Unexpected reload of MainServlet Date: Thu, 9 Jan 2003 18:42:59 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks, This seems to be the only option, although I am puzzled why the Tomcat container would release the reference to the servlet. Surely the point of being loaded on Tomcat startup is that servlet object is kept in continuous reference for the life cycle of the Tomcat instance - thereby never being garbage collected. Matt -----Original Message----- From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com] Sent: 09 January 2003 15:13 To: Tomcat Users List Subject: RE: Unexpected reload of MainServlet 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:matt@optimad.com] >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: unsubscribe@jakarta.apache.org> >For additional commands, e-mail: help@jakarta.apache.org> -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: