[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-937) Cannot have more than 64K instances of a clustered SFSB passivated

Wed Apr 4 23:08:07 EDT 2007

     [ http://jira.jboss.com/jira/browse/EJBTHREE-937?page=all ]

Brian Stansberry closed EJBTHREE-937.
-------------------------------------

    Resolution: Done

Resolved by adding another level to the Fqn.  Fqn is now /beanName/beanIdHash/beanId.  The beanIdHash level has 100 buckets, expanding the capacity to roughly 6.4 million beans.

> Cannot have more than 64K instances of a clustered SFSB passivated
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-937
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-937
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: AS 4.2.0 CR1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>
> The cache used for clustered SFSBs uses FileCacheLoader, which creates one directory per passivated bean instance.  This means the max number of passivated beans is affected by the filesystem's max number of child directories.  One of the causes of the issues reported in JBPAPP-90 is a load test is hitting a limit of ~ 64K nodes on a 64 bit ext3 filesystem.  Some google hits related to this make me think in some cases the limit might be 32K.
> The default removal timeout for ejb3 SFSBs is 0 (i.e. no removal), so hitting this limit is not far-fetched.
> Some possible solutions:
> 1) Add another layer to the Fqn, hash the bean id, and spread the beans among buckets.
> 2) Use another CacheLoader.

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