tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37356] - Tomcat does not invalidate sessions after session-timeout period has passed.
Date Tue, 07 Feb 2006 14:40:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37356>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37356





------- Additional Comments From jjliu@huawei.com  2006-02-07 15:40 -------
Do you mean that wo browsers use the same session to access a page, or just the
( quite usual ) case that two people use the web application?

A: not the same session. Different IE browser will generate differnt session 
ID.

That means in the included application B and C you get the session from
application A?

Application != context for you?

A: yes. 


So it seems that the common ground for all of us here is, that we have some
objects in the session that implement the HttpSessionBindingListener or
HttpSessionActivationListener.

A: I did not put any object implement the HttpSessionBindingLisener or 
HttpSessionActivationListener in the session.


I think with different thread ( when include the page in other application), 
when it will operate the session object, it will not synchronize the session 
object (or its filed accessCount).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message