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 Fri, 10 Mar 2006 08:40:14 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 amasson@kikamedical.com  2006-03-10 08:40 -------
(In reply to comment #20)

> Yes, that were my thoughts as well, but the ++ and -- operations (as in
> sessionCount++) are atomic because sessionCount is an int. They should not need
> to be synchronized according to the virtual machine specifications.

Generally this is not enough to have thread-safe code. For instance this kind of
code is not thread-safe:
  this.x--;
  if (this.x == 0) ...
In this case AtomicInteger.decrementAndGet can be used.

> 
> So the trigger has to be either the 64bit CPU / Java or Tomcat and mod_jk, or
> something in my configuration (the application is the same .war file)

Threading problems (ie lack of synchronization) are more visible on multi-CPU or
multi-core configurations.


-- 
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