Some additional information:

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?

Right now, even though I am using a clustered configuration of AS 5 CR2, I don't have another node joining the cluster, but I wouldn't expect the cache to be different based on that.

"bstansberry@jboss.com" wrote:
I'll have a look at how the choice of cache implementation is working in the absence of an explicit @CacheConfig annotation. I'm assuming there's no @CacheConfig annotation; please correct me if I'm wrong.

"ALRubinger" wrote:

"andy.miller@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

"ALRubinger" wrote:

"andy.miller@jboss.com" wrote:
I can probably reduce the code down to just the servlet and stateful session bean, and strip out the database access, and just put a sleep in the method implementation.

In the end we're going to need a more isolated case that may involve invocations on an SFSB alone, or preferably something to test Cache passivation directly. Then we may apply the same test to any of our cache implementations.

S,
ALR

Brian,

Sure thing. I don't have any ejb-jar.xml or jboss.xml files at all. I tried to use all the defaults as well (convention over configuration) for everything that I could. So here is the class declaration:

package services.ejb;

import java.io.Serializable;
import java.util.ArrayList;
import java.util.List;

import javax.ejb.Remove;
import javax.ejb.Stateful;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;

import org.jboss.annotation.ejb.Clustered;
import services.entities.Order;

@Clustered
@Stateful
public class OrderInquiryBean implements OrderInquiry, Serializable {

package services.ejb;

import java.util.List;
import services.entities.Order;

public interface OrderInquiry {

 public int getPaginationForInquiries();

 public List<Order> findOrdersByCustomer(long customerId);

 public void cancelSession();

}

"bstansberry@jboss.com" wrote:
Andy,

I misspoke before; it's driven by the org.jboss.ejb3.annotation.Cache annotation, not @CacheConfig.

"ALRubinger" wrote:
Andy:

And the test client?

S,
ALR