Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 55860 invoked from network); 21 Feb 2008 18:06:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2008 18:06:38 -0000 Received: (qmail 97788 invoked by uid 500); 21 Feb 2008 18:06:32 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 97520 invoked by uid 500); 21 Feb 2008 18:06:31 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 97509 invoked by uid 99); 21 Feb 2008 18:06:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 10:06:31 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of c1vamsi1c@gmail.com designates 216.239.58.191 as permitted sender) Received: from [216.239.58.191] (HELO gv-out-0910.google.com) (216.239.58.191) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 18:05:55 +0000 Received: by gv-out-0910.google.com with SMTP id p33so57498gvf.27 for ; Thu, 21 Feb 2008 10:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=9vChW5ritf1DxY2ezVolcEWOORTxInzdJ8bL2CiQhaE=; b=vfF63iRyiB7tAdL6P7QhyRkTb3AyvH3xD68bkonxFy6fnPLHg2I4mOzYRYSCl3Fou1gsP5fAv5idbs21R+w5U35mN5sRhUVLq1ZEi52cfww1EINx3VjZ2P5vy5brrKgP7Mr2QbF9JMa1oGQJ1Zinp7V67Tepsf8QDewBe/Q7q1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=L81tML/PNJHypOAbGDXZJmomlL/MpEc2a804RrcKxK5VWvNkODad6Z8SmrzDEK0MhQ/73j77sF3hDnciSwwBDl892izvFPq6M2d9OaudUSRn1+Q5lNOzSNUubceIOuVVMQNWqjEtHeBzre3CT+XJx2A21fN5KHfesFXwQb/8+6c= Received: by 10.142.72.21 with SMTP id u21mr7891685wfa.65.1203617161399; Thu, 21 Feb 2008 10:06:01 -0800 (PST) Received: by 10.142.14.8 with HTTP; Thu, 21 Feb 2008 10:06:01 -0800 (PST) Message-ID: <22d56c4d0802211006i19a1f4fbq6b0eb91ac393c6e2@mail.gmail.com> Date: Thu, 21 Feb 2008 23:36:01 +0530 From: "Vamsavardhana Reddy" To: dev@geronimo.apache.org, jacek@laskowski.net.pl Subject: Re: Geronimo Tomcat 2.0.3-SNAPSHOT: SESSIONS.ser written to workDir In-Reply-To: <22d56c4d0802202329l7da3a619y22d060eb8caf3725@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6466_16212336.1203617161375" References: <22d56c4d0802191537l2540f118kbe3020b6b4086ba4@mail.gmail.com> <1b5bfeb50802202144m68d90edbxba16e6128a0ada22@mail.gmail.com> <22d56c4d0802202329l7da3a619y22d060eb8caf3725@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_6466_16212336.1203617161375 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline BTW, this problem (or situation) applies to all versions of Geronimo. I have verified it on 1.1.1 and 2.0.3-SNAPSHOT versions. ++Vamsi On Thu, Feb 21, 2008 at 12:59 PM, Vamsavardhana Reddy wrote: > > > On Thu, Feb 21, 2008 at 11:14 AM, Jacek Laskowski > wrote: > > > On Tue, Feb 19, 2008 at 3:37 PM, Vamsavardhana Reddy > > wrote: > > > With Geronimo Tomcat 2.0.3-SNAPSHOT, when a web app is stopped, I am > > > noticing that the call to stop() in GeronimoStandardContext.kill() is > > making > > > the sessions to be written to a SESSIONS.ser under the workDir for the > > > application. But then destroy() called immediately is resulting in > > the > > > deletion of the workDir altogether. Under what situations will this > > workDir > > > be not deleted and how this SESSIONS.ser will be used/supposed to be > > used? > > > > What's 2.0.3-SNAPSHOT? I have never seen it mentioned before. > > It is the server built from branches\2.0. > > Should > > we care about it rather than pushing 2.1 to our end users? > > I think we should care about it too, for the users who are already using a > 2.0.x server may not want to move to 2.1 until 2.1 stabilizes a bit. > > > > Why are you > > working with the older version? > > My Win XP crashes when I build "geronimo-system" module from 2.1. I could > not figure the reason, but it has something to do with the model of my > ThinkPad :o(. > > > > > > Jacek > > > > -- > > Jacek Laskowski > > http://www.JacekLaskowski.pl > > > > ------=_Part_6466_16212336.1203617161375 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline BTW, this problem (or situation) applies to all versions of Geronimo.  I have verified it on 1.1.1 and 2.0.3-SNAPSHOT versions.

++Vamsi

On Thu, Feb 21, 2008 at 12:59 PM, Vamsavardhana Reddy <c1vamsi1c@gmail.com> wrote:


On Thu, Feb 21, 2008 at 11:14 AM, Jacek Laskowski <jacek@laskowski.net.pl> wrote:
On Tue, Feb 19, 2008 at 3:37 PM, Vamsavardhana Reddy
<c1vamsi1c@gmail.com> wrote:
> With Geronimo Tomcat 2.0.3-SNAPSHOT, when a web app is stopped, I am
> noticing that the call to stop() in GeronimoStandardContext.kill() is making
> the sessions to be written to a SESSIONS.ser under the workDir for the
> application.  But then destroy() called immediately is resulting in the
> deletion of the workDir altogether.  Under what situations will this workDir
> be not deleted and how this SESSIONS.ser will be used/supposed to be used?

What's 2.0.3-SNAPSHOT? I have never seen it mentioned before.
It is the server built from branches\2.0.

Should
we care about it rather than pushing 2.1 to our end users?
I think we should care about it too, for the users who are already using a 2.0.x server may not want to move to 2.1 until 2.1 stabilizes a bit.
 
Why are you
working with the older version?
My Win XP crashes when I build "geronimo-system" module from 2.1.  I could not figure the reason, but it has something to do with the model of my ThinkPad :o(.



Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl


------=_Part_6466_16212336.1203617161375--