[
http://jira.jboss.com/jira/browse/EJBTHREE-1367?page=all ]
Brian Stansberry closed EJBTHREE-1367.
--------------------------------------
Resolution: Done
Fixed by removing use of the pool from SFSB creation/destruction; now handled by
StatefulContainer itself.
A remaining issue is the creation of the pool is done in superclass Ejb3Container, but
AFAICT the pool is only used in StatelessContainer, not in StatefulContainer or
ServiceContainer. See EJBTHREE-1370.
InfinitePool makes SFSB passivation meaningless
-----------------------------------------------
Key: EJBTHREE-1367
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-1367
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA, AS 4.2.2.GA, AS 5.0.0.Beta4
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: AS 5.0.0.CR1
InfinitePool maintains a list of all objects that have been created and not yet removed.
For SFSBs this essentially functions as a second cache and makes passivation pointless,
since passivating from the SFSB cache doesn't remove the ref in the InfinitePool.
IIRC, the intent in 5.x is to get rid of the use of pools for SFSBs, but this is broken
in 4.x as well.
--
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