Return-Path: 
 <users-return-191344-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 17633 invoked from network); 6 Feb 2009 22:29:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Feb 2009 22:29:12 -0000
Received: (qmail 79507 invoked by uid 500); 6 Feb 2009 22:28:59 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 79477 invoked by uid 500); 6 Feb 2009 22:28:59 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 79466 invoked by uid 99); 6 Feb 2009 22:28:59 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 14:28:59 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of jrobertray@gmail.com
 designates 209.85.146.180 as permitted sender)
Received: from [209.85.146.180] (HELO wa-out-1112.google.com) (209.85.146.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 22:28:52 +0000
Received: by wa-out-1112.google.com with SMTP id v27so529241wah.16
        for <users@tomcat.apache.org>; Fri, 06 Feb 2009 14:28:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=vC20/R+SQy6QgzQBJjYMvO3QElBRqaZnD417a9K3aUs=;
        b=FmAkdSr7RcfwTUIXTRaJMAi72SLwo1ULNzzGxozTf8+phdXI45cEN52sftI061M+Sd
         KAPQiu6kHAQvCIpG0L/iaUTfdzlxeOjVCCZ8nhI2Nni4u5E9jOdfvfgbyy2fUNaiDqbk
         pOjU5s1UbqO/KTf7RZMZSMmDJMDYVL9Q2vWnY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=S7BwtPpec1RRnLj5JYr9k1/MV5YDi316vJzRjrbhAktGTrlXNL5tpSYuzun2BstoMH
         /EuxoBvthQC4H0QccOXnKCRXEjdjIpLWSrSMd3x9LWDswcNP8KECVA0nvMtXrED3cOc/
         WYxfUPOeu4WZdQfy4/nPGVEMQx5ArhXc52ULo=
MIME-Version: 1.0
Received: by 10.114.93.11 with SMTP id q11mr1543461wab.143.1233959312203;
 Fri,
	06 Feb 2009 14:28:32 -0800 (PST)
In-Reply-To: <498C8463.3000303@christopherschultz.net>
References: <2fe342af0902052005s4bdc79adrc7db8ff4df2efa83@mail.gmail.com>
	 <498C8463.3000303@christopherschultz.net>
Date: Fri, 6 Feb 2009 14:28:32 -0800
Message-ID: <2fe342af0902061428x5fa587e0i4872095e33a89f6d@mail.gmail.com>
Subject: Re: sessions lost after redeploy
From: J Robert Ray <jrobertray@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

On Fri, Feb 6, 2009 at 10:41 AM, Christopher Schultz
<chris@christopherschultz.net> wrote:
>> But if I copy a new .war into webapps, or touch the existing .war, so
>> that my app redeploys, my sessions are deleted.
>
> Are you sure that simply 'touch'ing the existing WAR causes your
> sessions to die? I can't account for that, but...

Yes, I am certain. Touch blows away the sessions. But tomcat
shutdown/restart preserves them.

I tried enabling debug message for the manager, with <Manager
debug="4" />, and I have my logger configured to show "ALL", but I
don't see any messages from the manager in my logs.

>
> If you recompile a class, the compiler assigns it a new serialVersionID
> (unless you specify one). If you have an object of a class (say,
> foo.bar.Baz) that was serialized with version X before the restart, and
> the class in the running server after the restart has version Y, then
> the object is not compatible and the de-serialization will fail. Are you
> getting any error messages? ClassCastException? Some weird versioning
> error? I have forgotten what the JVM says when these error occur...
> though the persistent session manager might ignore those errors.

I don't see anything relevant in the logs. My session consists of a
single value, a Byte[], so I shouldn't have a problem with
unserializable data. Besides, it reloads properly across a tomcat
restart.

Do you have an app that preserves sessions through a redeploy?

Thanks for your help!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org