[
http://jira.jboss.com/jira/browse/JBAS-3310?page=comments#action_12349490 ]
Brian Stansberry commented on JBAS-3310:
----------------------------------------
The original comment on this issue focused on the fact that remote sessions would not be
cleared in some edge cases. A likely much larger issue resulting from the same code error
is that an expiration check for every remote session will be performed once per check of a
single locally active session. Thus if there were 1,000 locally active sessions, and
1,000 remote sessions, a session expiration run would end up doing 1,000,000 remote
session expiration checks. This is a potentially very significant overhead.
Remotely initiated sessions are not cleared from the JBoss Cache upon
expiration
--------------------------------------------------------------------------------
Key: JBAS-3310
URL:
http://jira.jboss.com/jira/browse/JBAS-3310
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service, Clustering
Affects Versions: JBossAS-4.0.4.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-4.0.5.CR1, JBossAS-4.0.4.SP1
Any http session that is in the JBoss Cache due to remote replication but which has not
been accessed locally will not be cleared by the Tomcat background thread.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira