[jboss-jira] [JBoss JIRA] Resolved: (JBAS-2695) LRUStatefulContextCachePolicy implementation of maxBeanLife removal is flawed
[ http://jira.jboss.com/jira/browse/JBAS-2695?page=all ]
Ben Wang resolved JBAS-2695.
----------------------------
Fix Version/s: (was: JBossAS-4.0.5.CR1)
Resolution: Won't Fix
After some more thought, I really think this is not a critical issue anymore since it is
really a corner case and there is a workaround for ejb2. For ejb3, this won't apply.
So I am going to mark it as "Won't Fix" unless someone objects.
LRUStatefulContextCachePolicy implementation of maxBeanLife removal
is flawed
-----------------------------------------------------------------------------
Key: JBAS-2695
URL: http://jira.jboss.com/jira/browse/JBAS-2695
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-3.2.8RC1, JBossAS-4.0.3 SP1
Reporter: Scott M Stark
Assigned To: Ben Wang
Priority: Critical
The RemoverTask of the org.jboss.ejb.plugins.LRUStatefulContextCachePolicy performs
removal of passivated beans based on a maxBeanLife - maxBeanAge diff. This is invalid for
beans passivated due to size. The calculation should be maxBeanLife - (the per bean
instance time of inactivity). The reason is a bean may be passivated very quickly due to
cache size constraints and if the maxBeanLife - maxBeanAge == 0, just a quickly thrown
away.
--
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