[AXIS2-5118] In high load scenarios with many threads, the call to Introspector.getBeanInfo(Class,Class) causes high synchronization resulting in system stall

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.5.4
• Fix Version/s: 1.6.2, 1.7.0
• Component/s: adb
• Environment: Tomcat 7 with axis2 webservices
• Assignee: Andreas Veithen
• Reporter: Ronald Brindl
• Created: 11/Aug/11 13:15
• Updated: 28/Oct/11 22:22
• Resolved: 28/Oct/11 19:50

Description

I have a high load scenario, where a Clustered Web frontend does Webservice calls to a Backend Webservices.
There are around 200 Threads handling the webservices.
The CPU load of the machine went to near zero.
Using dynatrace, we realized, that all the calls went through BeanUtils.getPropertyQnameList, which in turn calls Introspector.getBeanInfo(beanClass, beanClass.getSuperclass());
This again calls WebAppClassLoader.loadClass(String name, boolean resolve), which is synchronized.

I fixed this problem by modifying BeanUtil.getPropertyQnameList so that it caches BeanInfo objects.

Issue Links

• duplicates: AXIS2-4524 Caching BeanInfo in adb module's BeanUtil improves performance
• duplicates: AXIS2-4878 Simple BeanInfo cache in BeanUtil.java helped us go from 48 second to 8 second request
• is duplicated by: AXIS2-5119 ComplexType array return performance issue