Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 7932 invoked by uid 500); 11 May 2001 02:17:38 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 7890 invoked from network); 11 May 2001 02:17:35 -0000 Message-ID: <20010511021741.57415.qmail@web11505.mail.yahoo.com> Date: Thu, 10 May 2001 19:17:41 -0700 (PDT) From: Michael Bergknoff Subject: Re: destroy/init sequence To: tomcat-dev@jakarta.apache.org In-Reply-To: <391742DC.7A51@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Bo, thanks for the comments. Let's move the discussion to the developer list and see if they have some comments. Thanks, Mike >>From: "Bo Xu" >>Reply-To: tomcat-user@jakarta.apache.org >>To: tomcat-user@jakarta.apache.org >>Subject: Re: destroy/init sequence >>Date: Sun, 06 May 2001 23:13:58 -0000 >> >>>From: Michael Bergknoff >>>Does the container maintain session state across >>>a destroy/init sequence? If so is it up to each >>>servlet to serialize or delete any objects stored >>>in the session? For debugging, is it possible to >>>control when the destroy method is called? >>> >>>Thanks, >>>Mike >>>[...] >> >> >>Hi :-) I am not sure: >>- IMHO, I think HttpSession doesn't has much relation >> with one special MyServlet, session is "of" >> webapps/container(not this webapp or that...), i.e., >> session is cross-webapp, so session is loaded by >> another classloader which is different from the webapp >> classloader which loads MyServlet. so even if the old >> webapp classloader is destroyed/GCed, the session object >> and its Class object and its classloader are still there. >>[...] >> > >Hi :-) I find a mistake in my last email:-) > >with TC4.0b1(standalone, JDK1.3, winnt40): >- session is "of" a special webapp, with the same browser: > % diferent webapp "has" different session > % diferent MyServlet in the same webapp "has" same session > >- when I updated MyServlet in webapp0, then MyServlet will be > reloaded, then the session of webapp0 will be a new > one(before it is expired) > > is the above right? why does the container destroy session > of a webapp when this webapp's classloader is updated? > > >have a nice day! :-) __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/