On 21/03/2011 08:52, Felix Schumacher wrote:
> On Sun, 20 Mar 2011 22:26:46 +0100, André Warnier wrote:
You are both right on some counts and both wrong on some counts.
The Servlet spec (section 7.6 in Servlet 3.0) requires that processing a
request associated with a session (i.e. has a session I
On Sun, 20 Mar 2011 22:26:46 +0100, André Warnier wrote:
Felix Schumacher wrote:
...
The creation or retrieval of a session, as far as I understand it,
is
totally under application control.
In other words, if your servlet (or JSP), when it is called,
executes
a HttpServletRequest.getSessio
umac...@internetallee.de
> To: users@tomcat.apache.org
> Subject: Re: Session timeouts: ignore "periodic polling" URL?
>
> On Sun, 20 Mar 2011 15:40:48 +0100, André Warnier wrote:
> > sebb wrote:
> >> On 20 March 2011 11:19, André Warnier wrote:
> >>> sol myr w
Felix Schumacher wrote:
...
The creation or retrieval of a session, as far as I understand it, is
totally under application control.
In other words, if your servlet (or JSP), when it is called, executes
a HttpServletRequest.getSession() call, then it will retrieve the
existing session (or creat
-date.
Unfortunately this prevents sessions from timing out...
Is there a way to tell Tomcat that some URL shouldn't affect
session
timeouts?
Namely if for the last 30 minutes, the browser requested nothing
but
"http://server/autoRefresh.do"; , then Tomcat should assume the
user
Ajax and
>>>> Comet), in order to keep the view up-to-date.
>>>> Unfortunately this prevents sessions from timing out...
>>>>
>>>> Is there a way to tell Tomcat that some URL shouldn't affect session
>>>> timeouts?
>>>> Namel
...
Is there a way to tell Tomcat that some URL shouldn't affect session
timeouts?
Namely if for the last 30 minutes, the browser requested nothing but
"http://server/autoRefresh.do"; , then Tomcat should assume the user went
away from the computer, and kill the session.
You may have
ortunately this prevents sessions from timing out...
>>
>> Is there a way to tell Tomcat that some URL shouldn't affect session
>> timeouts?
>> Namely if for the last 30 minutes, the browser requested nothing but
>> "http://server/autoRefresh.do";
x27;t affect session timeouts?
Namely if for the last 30 minutes, the browser requested nothing but
"http://server/autoRefresh.do"; , then Tomcat should assume the user went away
from the computer, and kill the session.
You may have to explain the logic of this a bit better, because on the
Hi,
We have a Servelts/JSP application Tomcat6.
Our javascripts issues automatic, periodic polling requests (Ajax and Comet),
in order to keep the view up-to-date.
Unfortunately this prevents sessions from timing out...
Is there a way to tell Tomcat that some URL shouldn't affect se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Siddhartha,
On 4/6/2009 1:50 PM, Siddhartha Purkayastha wrote:
> Looks like this should solve my problem -
> HttpSession.setMaxInactiveInterval() ?
That sounds like a good start.
> Are there any implications of using this method?
Yes: the session
Looks like this should solve my problem -
HttpSession.setMaxInactiveInterval() ?
Are there any implications of using this method?
2009/4/6 Siddhartha Purkayastha
> Hello All -
>
> How is it possible to implement variable session timeouts?
> My use case is: for a set of users
Hello All -
How is it possible to implement variable session timeouts?
My use case is: for a set of users with certain properties (which in turn
will be stored in the session, say x = 10), I want to have a time out of 30
mins. For others (say with property x = 15), I want to have a timeout of 1
:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 7:41 PM
To: Tomcat Users List
Subject: Re: Tomcat creates a jsessionid cookie when session timeouts
By the way, this behaviour only happens in Mozilla/Firefox, it does not
happen in Internet Explorer.
Regards,
Luís Amorim
Luis AMORIM/PT
Subject:Tomcat creates a jsessionid cookie when session
timeouts
Hi there.
I have the following problem occuring in my web application.
I am using struts and I am using the url rewriting method for session
maintenance, but when a timeout occurs the tomcat application server sets
a co
Hi there.
I have the following problem occuring in my web application.
I am using struts and I am using the url rewriting method for session
maintenance, but when a timeout occurs the tomcat application server sets
a cookie named jsessionid (used for session tracking purposes) with a new
sessio
xactly once and destroyed exactly once.
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 12:16 PM
To: Tomcat Users List
Subject: Re: Logging session timeouts
I still have a question about performance: any idea which of these
met
Listener:
A session is created exactly once and destroyed exactly once.
> -Original Message-
> From: David Kerber [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 09, 2006 12:16 PM
> To: Tomcat Users List
> Subject: Re: Logging session timeouts
>
>
, and have just
brought it along as needed... If someone knows for sure... Please let me
(us) know.
Tim
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 1:16 PM
To: Tomcat Users List
Subject: Re: Logging session timeouts
Thanks to both of yo
tion.
Tim
-Original Message-
From: Joey Geiger [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 12:27 PM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
While the user can delete the cookie that is associated with the session,
the server will consider the session
Thank you for the clarification.
-Original Message-
From: Tim Lucia [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 11:38 AM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
The filter, implementing HttpSessionListener, and binding itself to the
ses
rsday, February 09, 2006 12:27 PM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
While the user can delete the cookie that is associated with the session,
the server will consider the session valid until it times out, as the user
is unable to end the session manually. If yo
t the filter first. (If a user goes
inactive, the session will expire, and the listener will catch it and log
it)
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 11:09 AM
To: Tomcat Users List
Subject: Re: Logging session timeouts
Tha
EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 11:09 AM
To: Tomcat Users List
Subject: Re: Logging session timeouts
That got me going; thanks!
One more question:
Is there any way of telling if the session was actively invalidated, or
if it timed out? Looking at the docs for HttpSessionBinding
I don't believe so. Someone please correct me if I am wrong.
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 12:09 PM
To: Tomcat Users List
Subject: Re: Logging session timeouts
That got me going; thanks!
One more question:
Is
Users List
Subject: Re: Logging session timeouts
I got your code in, and it compiles, but I don't understand how I configure
the url-mapping you refer to. Could you point me to some docs for that? I
looked through the web.xml files (both the server one, and the one for the
app), but couldn't
)+milliseconds;
String secondsStr = (seconds<10 ? "0" : "")+seconds;
String minutesStr = (minutes<10 ? "0" : "")+minutes;
String hoursStr = (hours<10 ? "0" : "")+hours;
return new String(d
lt;100 ? "0" : ""))+milliseconds;
String secondsStr = (seconds<10 ? "0" : "")+seconds;
String minutesStr = (minutes<10 ? "0" : "")+minutes;
String hoursStr = (hours<10 ? "0" : "")
: Re: Logging session timeouts
I got your code in, and it compiles, but I don't understand how I configure
the url-mapping you refer to. Could you point me to some docs for that? I
looked through the web.xml files (both the server one, and the one for the
app), but couldn't find anything
{
return getClass().getName() + "#" + hashCode();
}
}
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 9:38 AM
To: Tomcat Users List
Subject: Logging session timeouts
Is there any way of trapping session timeou
inal Message-
From: Joey Geiger [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 8:48 AM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
Session Listeners
http://pdf.coreservlets.com/CSAJSP-Chapter9.pdf
-Original Message-
From: David Kerber [mailto:[
}
/**
* Return string representation of this object
* @return a String representation of this object
*/
public String toString()
{
return getClass().getName() + "#" + hashCode();
}
}
-Original Message-
From: David Kerber [mailto:[EMAIL PROTE
Session Listeners
http://pdf.coreservlets.com/CSAJSP-Chapter9.pdf
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 8:38 AM
To: Tomcat Users List
Subject: Logging session timeouts
Is there any way of trapping session timeouts, so I can
Code();
}
}
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 9:38 AM
To: Tomcat Users List
Subject: Logging session timeouts
Is there any way of trapping session timeouts, so I can log them? I am
logging when a user
Is there any way of trapping session timeouts, so I can log them? I am
logging when a user logs in and when they explicitly log out, but would
like to log when their session times out, if that is possible.
TIA!
Dave
-
To
I am having some problems with session timeouts. I set the session-timeout
property to 15 minutes in the Tomcat global web.xml and also in my application
web.xml. However, Tomcat is not always timing out when sessions are inactive
more than 15 minutes.
On some systems, it behaves as I expect
36 matches
Mail list logo
