[jboss-user] [EJB 3.0 Development] New message: "Re: Default remove timeout"

[jaikiran pai]

User development,

A new message was posted in the thread "Default remove timeout":

http://community.jboss.org/message/529011#529011

Author  : jaikiran pai
Profile : http://community.jboss.org/people/jaikiran

Message:
--------------------------------------------------------------
I think the remove() implementation could easily be changed from: 
public void remove(Object key)
{
  if(log.isTraceEnabled())
  {
     log.trace("Removing context " + key);
  }
  StatefulBeanContext ctx = null;
  synchronized (cacheMap)
  {
     ctx = cacheMap.get(key);
  }
  if(ctx == null)
     throw new NoSuchEJBException("Could not find Stateful bean: " + key);
...
 

 
to 
 
public void remove(Object key)
{
  if(log.isTraceEnabled())
  {
     log.trace("Removing context " + key);
  }
  // don't use the cacheMap directly. Instead let's call get()
  // which activates any passivated sessions.
  StatefulBeanContext ctx = this.get(key);
  if(ctx == null)
     throw new NoSuchEJBException("Could not find Stateful bean: " + key);
...
 

 
because the implementation of get() already has logic to check the passivation queue as well as the persistence manager to see first activate any passivated sessions.
 
I'll file a EJBTHREE JIRA for this

--------------------------------------------------------------

To reply to this message visit the message page: http://community.jboss.org/message/529011#529011