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

[andy.miller@jboss.com]

"bstansberry at jboss.com" wrote : "andy.miller at jboss.com" wrote : Is it possible that what you are testing is not what is in the CR 2 build?
  | 
  | Oh, for sure. I'm testing my local checkout of trunk, which is probably off from head by a day or so.
  | 
  | Hmm, I see what you are saying about the maxSize in the JMX console. I'll have a look; that's a bug.  When I tracked the deployment in the debugger, the 100K maxSize came through from the metadata and was passed into the JBC eviction configuration. So 99% sure the bug is in the JMX display of the metadata.

Based on your test, that's what I was starting to think as well.  So, that leaves me with one other issue to explore.  Why is my test so much slower using the StatefulTreeCache, then using the SimpleStatefulCache?

I have been having trouble with getting JBoss Profiler working, but Jesper has given me a fix for an issue I was having.  Could you recommend specific packages I should make sure I capture with the profiler?

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

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