Incorrect handling of timestamps in clustered session ----------------------------------------------------- Key: JBAS-7091 URL: https://jira.jboss.org/jira/browse/JBAS-7091 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.2.0.Beta1 ClusteredSession has an "outdatedTime" field that records the timestamp when a session gets a callback notifying of a modification on another node. If the session state later gets updated from the distributed cache, the clearOutdated() method ends up setting the session timestamp to that "outdatedTime" rather than the correct timestamp that's stored in the distributed cache. That's wrong. Not a big deal, as the difference between the outdatedTime and the correct timestamp is probably just a few ms (time it takes to replicate the session). But still, it's wrong. In any case the handling of "outdatedTime" is more complex than need and related "outdatedVersion" field can be removed altogether. There's a bit of cruft here from the old days when correct timestamps weren't readily available from the cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira