[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2050) Ensure ids for newly created SFSB contexts will hash locally in Infinispan
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Thu Oct 28 00:11:54 EDT 2010
[ https://jira.jboss.org/browse/EJBTHREE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro resolved EJBTHREE-2050.
------------------------------------
Resolution: Done
> Ensure ids for newly created SFSB contexts will hash locally in Infinispan
> --------------------------------------------------------------------------
>
> Key: EJBTHREE-2050
> URL: https://jira.jboss.org/browse/EJBTHREE-2050
> Project: EJB 3.0
> Issue Type: Sub-task
> Components: cache, Clustering
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
>
> If Infinispan DIST is used, at least one of the cache locations for an SFSB should be the node that created it. This way in the normal case where there are 2 copies, a single unicast to the backup node is sufficient to replicate. If the cache key (the SFSBContext id) hashes to 2 remote nodes, then every cache write will require 2 unicasts.
> The problem here is unlike web sessions, the id for an SFSB context is not generated by the caching layer; it's generated by StatefulBeanContext itself. So the web session strategy of having a background thread occasionally populate a pool of ids that are known to map locally (using the consistent hash algorithm Mircea Marcus is going to expose for ISPN-232) won't work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list