Scott's follow up comment:

A bean with an active method cannot be passivated and the reason we do not 
obtain the lock is described in a comment right before the attemptSync call 
about a deadlock problem. Not passivating is not a huge deal in general as it 
should only result in a transient excess of beans. The removal of the bean from 
the cache is a problem.
 
To block the call, the deacklock problem would have to be revisted to validate 
what is going on. There is a user forum post saying that we are creating sfsb 
instances that end up being thrown away if the session is activated so we may 
need to revisit the cache behavior. We could also have a notion of lazy 
passiviation that would result in marking the bean as would have been 
passivated so that it can be passivated after the current call ends. One 
potential problem with this is that time based passivation that fails to 
passivate an active instance should simply fail as its a race condition between 
the background timer and active usage. We should discuss the issues in the 
forums as I'm sure Bill has other cache implementations in ejb3 that need to be 
validated as well.


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917076#3917076

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917076


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to