Save This Page
Home » jboss-5.0.0.CR1-src » org » jboss » ejb » plugins » [javadoc | source]
org.jboss.ejb.plugins
public class: StatefulHASessionInstanceCache [javadoc | source]
java.lang.Object
   org.jboss.ejb.plugins.AbstractInstanceCache
      org.jboss.ejb.plugins.StatefulSessionInstanceCache
         org.jboss.ejb.plugins.StatefulHASessionInstanceCache

All Implemented Interfaces:
    MetricsConstants, XmlLoadable, AbstractInstanceCacheMBean, Monitorable, InstanceCache

SFSB cache for clustered environment. Mainly avoid "excessive" locking that can generate cluster-distributed deadlocks.
Fields inherited from org.jboss.ejb.plugins.AbstractInstanceCache:
log
Method from org.jboss.ejb.plugins.StatefulHASessionInstanceCache Summary:
get,   invalidateLocally
Methods from org.jboss.ejb.plugins.StatefulSessionInstanceCache:
acquireContext,   activate,   canPassivate,   destroy,   doActivate,   freeContext,   getContainer,   getKey,   getPassivatedCount,   passivate,   postRemovalCleanup,   preRemovalPreparation,   removePassivated,   setContainer,   setKey
Methods from org.jboss.ejb.plugins.AbstractInstanceCache:
acquireContext,   activate,   canPassivate,   create,   destroy,   doActivate,   flush,   freeContext,   get,   getCache,   getCacheLock,   getCachePolicyString,   getCacheSize,   getContainer,   getKey,   getPassivatedCount,   importXml,   insert,   isActive,   logActivation,   logPassivation,   passivate,   release,   remove,   resetStatistic,   retrieveStatistic,   sample,   setKey,   start,   stop,   tryToPassivate,   tryToPassivate,   unableToPassivateDueToCtxLock
Methods from java.lang.Object:
equals,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.jboss.ejb.plugins.StatefulHASessionInstanceCache Detail:
 public EnterpriseContext get(Object id) throws NoSuchObjectException, RemoteException 
 public  void invalidateLocally(Object id) 
    Remove an object from the local cache *without* any locking (synchronized, etc.) to avoid huge cluster-wide deadlock situations We have to unschedule passivation as well as the bean may be used on another node.