"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.
The issue is clearly passivation. The passivation count is zero on the first occurrence,
and everything hangs, and then the passivation count is non-zero. The only time the hang
occurs is when passivation happens. My typical response times on calling the stateful
session bean and returning with the result set are between 7 and 40ms.
This is being run on Fedora 9, with our OpenJDK 6 JVM.
After rebuilding with the AS 5 CR 2 libraries, the problem does go away, because I now
have confirmed that I'm using the StatefulTreeCache, which is the default in the
ejb3-interceptors-aop.xml based on the fact that I only have the @Clustered annotation:
| <!-- Clustered cache configuration -->
| <annotation expr="!class((a)org.jboss.ejb3.annotation.Cache) AND
class((a)org.jboss.ejb3.annotation.Clustered)">
| @org.jboss.ejb3.annotation.Cache ("StatefulTreeCache")
| </annotation>
| <annotation expr="!class((a)org.jboss.ejb3.annotation.CacheConfig) AND
class((a)org.jboss.ejb3.annotation.Clustered)">
| @org.jboss.ejb3.annotation.CacheConfig
(name="jboss.cache:service=EJB3SFSBClusteredCache", maxSize=100000,
idleTimeoutSeconds=300, removalTimeoutSeconds=0)
| </annotation>
|
Clearly the synchronization in the SimpleStatefulCache is a real problem. If I
weren't running in a clustered configuration (and didn't have the issue I had
because I didn't rebuild with the AS 5 libraries), I would still have the same
problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184001#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...