Ok, this is currently related to SFSB case that is reported from the customer. 
Basically, here is the problem description:

Basically, in SFSB, if you configure the max pool size to 2, but I have more 
than 2 threads accessing the SFSB container, there can be a problem. Let?s say 
bean1 and bean2 have been created. When another thread trying to create bean3, 
it will have to passivate bean2 first. But during the passivation stage, in 
AbstractInstaceCache.tryToPassivate(), it will try to obtain the lock by 
calling lock2.attemptSync(). Problem is during this period, another thread have 
been accessing bean2 and therefore obtain the lock already. 

As a result, tryToPassivate() would fail and report ?unable to passivate? 
error. Still, it will remove the cache entry from the map (this is a bug, IMO). 
So next time around, activation would fail because it never get passivated.

 I am think that we should block, i.e., lock2.attempt(secs) instead. However, 
there can be another problem as Scott's comment below indicates.

If we don't block, option is to throw exception to the thread that is creating 
bean3. But this can happen frequently is bean pool size is small  and it is 
highly concurrent.

 

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

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


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