[SM-2069] SourceTransformer should cache DocumentBuilder & TransformerFactory

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: servicemix-utils-1.5.0
• Fix Version/s: servicemix-utils-1.5.0
• Component/s: servicemix-utils

Environment

http://svn.apache.org/repos/asf/servicemix/utils/trunk

• Patch Info: Patch Available
• Assignee: Freeman Yue Fang
• Reporter: Jonathan Anstey
• Created: 19/Apr/11 12:22
• Updated: 20/Apr/11 11:12
• Resolved: 20/Apr/11 03:38

Description

I noticed that when routing between JBI endpoints in Camel like:

from("jbi:endpoint:serviceNamespace:serviceA:endpointA").to("jbi:endpoint:serviceNamespace:serviceB:endpointB");

There is a huge overhead creating new TransformerFactory and DocumentBuilder objects. After caching these on a per thread basis I was able to get a test case down from 41.583 sec to 18.224 sec.

To test this, apply the attached patch (cache_docbuilder.patch) to the servicemix-utils trunk, and also modify the servicemix-camel component with the attached patch (cache_docbuilder_test.patch) and run the following:

janstey@duffman:/x1/asf/servicemix/components/trunk/engines/servicemix-camel$ mvn clean test -Dtest=SendFromCamelToJbiThenRouteToAnotherJbiComponentTest

You may need to up surefire's Xmx as well.

If someone is going to commit this, please only commit the code in cache_docbuilder.patch