"wolfc" wrote : That takes care of the cache configuration, but I also want to
know what's behind this passivation issue.
|
| Is passivating or activating the culprit?
| On what OS is this?
|
| If it was the sync on cacheMap I would say a deadlock would happen, not some timeout
of 30 seconds.
Needs to be proven of course, but SimpleStatefulCache.SessionTimeoutTask holds a lock on
the cacheMap while it iterates through the contents and passivates. If there are a lot of
beans (knowing Andy, this is a load test and there are) that could take a while. Any
SimpleStatefulCache.get() request will block in the meantime.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183977#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...