May 2009 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: EJBTHREE-1800 Current status on performance improvement

by jaikiran

I looked at the profiler snapshot today to see for any further major improvements that can be brought in. Here's the summary on where the majority of time is spent (in short, AOP and annotation scanning) The scenario being considered is 100 beans (simple ones) with 100 methods each and one @Resource and one @EJB injection each. 1) During EJB3 deployment, for each of these beans a bean container is created. During initialization of this bean container, the (expensive) AOP initialization is done, which includes creating AOP interceptor chain, applying any bindings to each of the 100 methods for each of the 100 beans. As the number of methods increases, so does the time. 2) Once the bean container is initialized (and AOP initialized for this bean container), these containers are again reinitialized for AOP (can't be avoided as explained by Carlo and ALR). So this leads to a second iteration of expensive AOP initialization 3) The next part where time is being spent is annotation scanning. *Each method on each bean* is scanned for various methods at different points: 3a - InterceptorRegistry - Looks for annotations like @Interceptors, @ExcludeDefaultInterceptors @ExcludeClassInterceptors and so on. 3b - Factories (like CMTTxInterceptorFactory) in AOP interceptor chain which is applied to the methods, looks for annotations like @TransactionTimeout, @TransactionAttribute and so on 3c - Then there is MC which scans all methods of all MC bean instances (bean containers are deployed as MC beans) for any MC specific annotations and other custom annotations, which can be processed by AnnotationPlugins. The process of annotation scanning goes through the AOP advisor which invokes the corresponding retrievals (EJB3 has some custom metadata bridges which resolve annotations out of EJB3 metadata) for 3a, 3b and 3c. As the number of methods increases, so does the time to do all this. I was looking for an API like - getAnnotations(Member m) and getClassAnnotations() which when invoked would get all the available annotations on a member or a class. Later on when anyone requires to check for an annotation, the repository could then use this internal cache. However, from what i found in the code, these APIs aren't implemented/available. There are some improvements that can help improve the performance: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154878 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154875 However, these couple of changes wont bring in a major improvement in performance. Overall, its AOP stuff that we need to think about to bring in some considerable improvements. Any ideas are welcome - i can give them a try. In the meantime, i'll look for any changes that might bring in some difference. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229027#4229027 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229027

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1800 Current status on performance improvement

by jaikiran

anonymous wrote : 2. add annotations in Ejb3DescriptorHandler Looked at this code now (i was refering to Ejb3AnnotaitonHandler earlier). This piece of code creates annotations for descriptor based deployments. Hmm, maybe we could add a conditional reinitialization? Reinitialize if its a descriptor based deployment (i.e. annotations have been added after AOP initialization)? But again, the performance gain with this change, will only be seen when the application is annotation based. Thoughts? "ALRubinger" wrote : The re-initialization includes the "virtual" methods to be advised - the EJB business method map. | | S, | ALR >From what i see in ExtendedManagedObjectAdvisor, it's done even during normal initialization. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229009#4229009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229009

16 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: REST integration within JBoss ESB

by clandestino_bgd

Hi, anonymous wrote : | I think the biggest trick is how all the HTTP headers, request content, and response body are mapped to the ESB message and made available in actions. | +1 In general, it would be nice if esb can support: - rest service consuming (resteasy client impl is very good) - rest service exposing (esb service deploy as rest) Making resteasy the 1st class citizen of esb (with appropriate support from jboss tools) would be great. Alternatively, maybe you can take a look at enunciate: http://enunciate.codehaus.org/ best, milan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229007#4229007 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229007

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task completion without outcome?

by kukeltje

and why not have it take the default transition if there is more then one? complete() and complete(null) would be the same then... not completely illogical View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228998#4228998 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228998

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task completion without outcome?

by tom.baeyens＠jboss.com

https://jira.jboss.org/jira/browse/JBPM-2221 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228987#4228987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228987

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Jax-RPC WS Implementation in JBoss

by richard.opalka＠jboss.com

We highly recommend you to migrate your application to JAX-WS. JAX-RPC will be removed from J2EE specification soon. And next time please post your user quesitions to our user forums. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228985#4228985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228985

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task completion without outcome?

by tom.baeyens＠jboss.com

ok. i see the point. so we both think that complete(null) should take the single outgoing transition if there is one. but the implementation doesn't do that. right ? i'll create a jira for it View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228975#4228975 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228975

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Enforce transition names?

by kukeltje

anonymous wrote : users should only be forced to specify transition names if it has a meaning/purpose for the user. When is that? For me in almost any case. Certainly in decisions (at least without guarded transitions, but that is impossible in xsd's) but also in tasknodes, so for me it is better to enforce it always. Forks in my experience were limited to 4 legs so it is not a real problem. Besides that it is very easily enforced in an xsd. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228974#4228974 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228974

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Enforce transition names?

by tom.baeyens＠jboss.com

signal without parameter signalExecutionById(String executionId) or signalExecutionById(executionId, (String)null) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228972#4228972 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228972

16 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1800 Current status on performance improvement

by ALRubinger

The re-initialization builds includes the "virtual" methods to be advised - the EJB business method map. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228968#4228968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228968

16 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009