Return-Path: 
 <users-return-138334-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 53098 invoked from network); 10 Jan 2006 06:45:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 10 Jan 2006 06:45:34 -0000
Received: (qmail 19171 invoked by uid 500); 10 Jan 2006 06:45:22 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 18360 invoked by uid 500); 10 Jan 2006 06:45:18 -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 18349 invoked by uid 99); 10 Jan 2006 06:45:18 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 22:45:18 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=HTML_MESSAGE
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [203.89.192.138] (HELO mail.app.aconex.com) (203.89.192.138)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2006 22:45:17 -0800
Received: from page.mel.office.aconex.com (page.mel.office.aconex.com
 [192.168.0.210])
	by mail.app.aconex.com (Postfix) with ESMTP id 4AF755B8047
	for <users@tomcat.apache.org>; Tue, 10 Jan 2006 17:44:56 +1100 (EST)
Received: from localhost (page.mel.aconex.com [127.0.0.1])
	by page.mel.office.aconex.com (Postfix) with ESMTP id 34D90534156
	for <users@tomcat.apache.org>; Tue, 10 Jan 2006 17:44:56 +1100 (EST)
Received: from page.mel.office.aconex.com ([127.0.0.1])
 by localhost (mail.aconex.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 07327-01-27 for <users@tomcat.apache.org>;
 Tue, 10 Jan 2006 17:44:54 +1100 (EST)
Received: from [192.168.0.242] (unknown [192.168.0.242])
	by page.mel.office.aconex.com (Postfix) with ESMTP id 71E44534155
	for <users@tomcat.apache.org>; Tue, 10 Jan 2006 17:44:54 +1100 (EST)
Mime-Version: 1.0 (Apple Message framework v746.2)
To: users@tomcat.apache.org
Message-Id: <3E626E33-0B2C-424D-A76F-8452218CD746@aconex.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-11--345497822
From: Paul Smith <psmith@aconex.com>
Subject: JDBC Session Persistence in a cluster problem/question
Date: Tue, 10 Jan 2006 17:44:52 +1100
X-Mailer: Apple Mail (2.746.2)
X-Virus-Scanned: amavisd-new at aconex.com
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

--Apple-Mail-11--345497822
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

	From: 	  psmith@aconex.com
	Subject: 	JDBC Session persistence in a cluster problem/question
	Date: 	10 January 2006 5:42:51 PM
	To: 	  user@tomcat.apache.org

[For context, Tomcat 5.5.12]

Hello all,

I'm having a bit of trouble understanding exactly what the  
capabilities are of the whole PersistenceManager and how it saves  
session data.  here's what I we have configured in server.xml:

        <Host name="localhost" appBase="foo" >
                 <Context path="/" docBase="${catalina.home}/app/mel/" >
                  <Manager  
className="org.apache.catalina.session.PersistentManager" >
                         <Store  
className="org.apache.catalina.session.JDBCStore"
                          
connectionURL="jdbc:inetdae7:tower.aconex.com? 
database=paul&amp;user=sql&amp;password=sql"
                         driverName="com.inet.tds.TdsDriver"
                         sessionIdCol="session_id"
                         sessionValidCol="valid_session"
                         sessionMaxInactiveCol="max_inactive"
                         sessionLastAccessedCol="last_access"
                         sessionTable ="tomcat_sessions"
                         sessionAppCol = "app_name"
                         sessionDataCol = "session_data"
                         />
                  </Manager>
         </Context>
         </Host>

Sessions are persisting, as we can see the new rows being added to  
the DB.  Fine, great.

However in our test cluster environment we have noticed that session  
variables (strings, Integers) are being "lost" during the failover to  
the other node in the cluster.  From looking at the Javadoc of the  
PersistentManager and other related info on the net, I can't see  
anywhere where it indicates that the Session is persisted to the DB  
when the session is updated/modified/addedto.  It seems to only have  
settings that set how long to wait before saving to the persistence  
store.

1). Am I correct in my understanding so far?
2) . If so, is this design because of the likely performance impact  
of all these session changes, and the somewhat unlikely case of the  
server going down in the first place.
3). do I have any options here?  We really do need a pretty seamless  
failover with session information being kept in sync as it failsover  
to the other node in the cluster.

cheers,

Paul Smith


--Apple-Mail-11--345497822--