[jboss-dev-forums] [Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

[andy.miller@jboss.com]

"ALRubinger" wrote : "andy.miller at jboss.com" wrote : I tested changing the cache maxSize parameter with ejb3-interceptors-aop.xml, and discovered that I am actually using the SimpleStatefulCache.  I'm not really sure why.  Perhaps something I need to have on the @Clustered annotation?
  | 
  | This shouldn't be.  We add the proper default annotations if not specified in AOP (ejb3-interceptors-aop.xml):
  | 
  |       <!-- Clustered cache configuration -->
  |   |       <annotation expr="!class(@org.jboss.ejb3.annotation.Cache) AND class(@org.jboss.ejb3.annotation.Clustered)">
  |   |          @org.jboss.ejb3.annotation.Cache ("StatefulTreeCache")
  |   |       </annotation>
  |   |       <annotation expr="!class(@org.jboss.ejb3.annotation.CacheConfig) AND class(@org.jboss.ejb3.annotation.Clustered)">
  |   |          @org.jboss.ejb3.annotation.CacheConfig (name="jboss.cache:service=EJB3SFSBClusteredCache", maxSize=100000, idleTimeoutSeconds=300, removalTimeoutSeconds=0)
  |   |       </annotation>
  | 
  | S,
  | ALR

I do have what you list above in my configuration.  Just before it is also the non-clustered configuration, and that is what I'm picking up, based on my experimentation.

I think Brian will discover a problem with the way this is being selected when there is no @CacheConfig annotation.

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

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