This is helpful regarding this problem:
http://www.jboss.org/community/wiki/JbossTimeoutSettingForSeam
It states that serializability problems may be the root cause of this exception
as well. But if that's true, wouldn't you get serializable/passivation
exceptions in the server.log? I've seen
"boobalan_kj" wrote : Hi
|
| you could control life time of bean by using the following configurations...
|
|
| Standard Stateful SessionBean
|
|
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy
|
| 50
| 100
|
thank you!
btw, I found the answer to my first question.
ejb3-interceptors-aop.xml:
| ...
|
| @org.jboss.annotation.ejb.cache.simple.CacheConfig
(maxSize=10, idleTimeoutSeconds=3600)
|
| ...
|
View the original post :
http://www.jboss.com/index.h
Hi
you could control life time of bean by using the following configurations...
Standard Stateful SessionBean
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy
50
100
300
300
200
600
400
