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

[andy.miller@jboss.com]

"andy.miller at jboss.com" wrote : "ALRubinger" wrote : "andy.miller at 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
  |   | 
  |   | 
  | 
  | I will work on cutting out just the code for the Stateful Session Bean, so it can be turned into an isolated test case tomorrow.

I have been struggling to create a more isolated test case that's easy to run.  I have a test case that is creating lots of Stateful Session Beans, but I can't get them to be cached (other than one bean at a time).  What causes the bean to be cached, and then eventually passivated?

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

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