October 2008 - jboss-dev-forums - Jboss List Archives

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

by andy.miller＠jboss.com

"ALRubinger" wrote : "andy.miller(a)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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183373#4183373 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183373

16 years

1
0
0 / 0

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

by andy.miller＠jboss.com

"ALRubinger" wrote : "andy.miller(a)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): | |  | | <annotation expr="!class((a)org.jboss.ejb3.annotation.Cache) AND class((a)org.jboss.ejb3.annotation.Clustered)"> | | @org.jboss.ejb3.annotation.Cache ("StatefulTreeCache") | | </annotation> | | <annotation expr="!class((a)org.jboss.ejb3.annotation.CacheConfig) AND class((a)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

16 years

1
0
0 / 0

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

by andy.miller＠jboss.com

"bstansberry(a)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. Yes, you are correct, there is not @CacheConfig annotation. Only the @Clustered annotation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183371#4183371 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183371

16 years

1
0
0 / 0

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

by ALRubinger

"andy.miller(a)jboss.com" wrote : I tested changing the cache maxSize parameter with ejb3-interceptors-aop.xml, and discovered that I am actually using the SimpleStatefulCache. Something I noted w/ SimpleStatefulCache: Without seeing this firsthand, my educated guess is in SessionTimeoutTask.run() where we synchronize on the entire SimpleStatefulCache.cacheMap to do passivation; this will queue up all other Threads looking to create or get a session as they wait to acquire the lock. http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/core/src/main/... S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183369#4183369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183369

16 years

1
0
0 / 0

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

by ALRubinger

"andy.miller(a)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):  | <annotation expr="!class((a)org.jboss.ejb3.annotation.Cache) AND class((a)org.jboss.ejb3.annotation.Clustered)"> | @org.jboss.ejb3.annotation.Cache ("StatefulTreeCache") | </annotation> | <annotation expr="!class((a)org.jboss.ejb3.annotation.CacheConfig) AND class((a)org.jboss.ejb3.annotation.Clustered)"> | @org.jboss.ejb3.annotation.CacheConfig (name="jboss.cache:service=EJB3SFSBClusteredCache", maxSize=100000, idleTimeoutSeconds=300, removalTimeoutSeconds=0) | </annotation> S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183367#4183367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183367

16 years

1
0
0 / 0

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

by ALRubinger

"andy.miller(a)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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183366#4183366 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183366

16 years

1
0
0 / 0

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

by bstansberry＠jboss.com

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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183364#4183364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183364

16 years

1
0
0 / 0

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

by andy.miller＠jboss.com

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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183362#4183362 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183362

16 years

1
0
0 / 0

[Design of EJB 3.0] - Passivating EJB 3 Stateful Session Beans stops the World!

by andy.miller＠jboss.com

Carlo and Andrew, I have been running the same load test that I ran for my EAP 4.x performance tuning presentation (uses the EJB 3 Stress Test application we use in QE), and I have discovered what appears to be a pretty major problem. When I first kick-off a run, everything is running quite smoothly and I am actually getting slightly higher results than with EAP 4.2. Then everything just stops. The test just seems to be hung for anywhere between 30 seconds and a minute. Then everything starts again, and it runs like it was running before. In trying to correlate what was happening I found something quite interesting. In looking at the JMX console for my stateful session bean, I can see that when everything stops, is when the container is passivating bean instances. In fact, when everything stops, that is the only time that the passivation counts increments in the JMX console. On EAP 4.2/4.3 I noticed similar behavior, but never correlated it to anything, because it would stop only for 5 to 10 seconds, never this extended period of time. Even with these hangs, we are only about 8% slower than before, and if these hangs were eliminated, we would be faster by about 3%. Of course, I am using OpenJDK 6, versus using the Sun JDK 5, and the improvement may be just because of the JVM, but even if that is the case, we are probably a wash in terms of performance. In any case, this is a serious issue that needs investigation. Here is some more relevant information: The default cache configuration is being used, which should be the StatefulTreeCache, since I have the @Clustered annotation on my stateful bean. 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183361#4183361 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183361

16 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Reflect and MDR going GA

by alesj

"adrian(a)jboss.org" wrote : | It's either "hold your peace" or "say your piece". | "Holding your piece" could mean something very different! | That's what I meant. But I was unlucky to either get the first word right or spell 'peace' right. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183338#4183338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183338

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008