Return-Path: 
 <tomcat-user-return-84770-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 22820 invoked from network); 25 Nov 2003 00:00:33 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 25 Nov 2003 00:00:33 -0000
Received: (qmail 38863 invoked by uid 500); 24 Nov 2003 23:59:58 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 38736 invoked by uid 500); 24 Nov 2003 23:59:57 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 38721 invoked from network); 24 Nov 2003 23:59:57 -0000
Received: from unknown (HELO gateway1.monsanto.com) (199.89.234.134)
  by daedalus.apache.org with SMTP; 24 Nov 2003 23:59:57 -0000
Received: from agstlsmtp02.monsanto.com (agstlsmtp02.monsanto.com
 [10.30.64.102])
	by gateway1.monsanto.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
 hAP003v8022649
	for <tomcat-user@jakarta.apache.org>; Mon, 24 Nov 2003 18:00:03 -0600 (CST)
Received: by agstlsmtp02.monsanto.com with Internet Mail Service (5.5.2653.19)
	id <XL9N1CGH>; Mon, 24 Nov 2003 18:00:03 -0600
Message-ID: <9548328D5FFCD411BB7A00508BAFB94D17B96D5D@ems1000-07.monsanto.com>
From: "WALKUP, RON [AG/1000]" <ron.walkup@monsanto.com>
To: "'tomcat-user@jakarta.apache.org'" <tomcat-user@jakarta.apache.org>
Subject: definition/usage of session-timeout?
Date: Mon, 24 Nov 2003 18:00:03 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Hi,
    I'm a relatively new Tomcat user, running 4.0.4 (testing on Windows, deploying on Sun UNIX).  The UNIX servlet is having rare problems "hanging", for which the exact cause is unknown.

I'm trying to see if a session timeout can solve the problem, but have not been able to get it to work.  Numerous archives talk about this, and it seems like I'm doing what everyone suggests, but it's not working.

In my web.xml file, I have the following, as a test of one-minute timeout:

  <session-config>
      <session-timeout>1</session-timeout>
   </session-config>

I have made a call the HttpSession.getMaxInactiveInterval, and it returns 60 (seconds, I presume), so I believe the parameter is being applied.  I have tried 2 different approaches to simulate an "inactive" server:

1)  Manually update a database row (but don't commit) before the servlet call, then have the servlet try to update the same row
2)  Use Thread.sleep(120000)

In both cases, the 1 minute timeout doesn't do anything.  So what constitutes an "inactive" session, for which this parameter was designed?  If it likely won't solve my problem, does anyone have an idea on how I can kill the request after a given amount of time?


much thanks,

-Ron

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