[
https://issues.apache.org/jira/browse/XALANJ-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992010#comment-12992010
]
Tom Hutchinson commented on XALANJ-2533:
----------------------------------------
We have been having this exact same issue where we had 16 threads trying to use
XPath on different XML at the same time and found it blocking down in the Xalan
code. Following the thread stack trace I found DTMManager.newInstance() being
called and looked at the Javadoc for it on what it's trying to do. Since we
had no system property set it searches for the factoryId in every jar file on
every call to this method.
http://xml.apache.org/xalan-j/apidocs/org/apache/xml/dtm/DTMManager.html#newInstance%28org.apache.xml.utils.XMLStringFactory%29
Just by setting the system property to the default it will not do this lookup
every single time and substantially improve performance.
org.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault
> DTMManager.newInstance issue in a java multithreaded application: excessive
> ClassLoader, threads lock wait, no cache
> --------------------------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2533
> URL: https://issues.apache.org/jira/browse/XALANJ-2533
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: DTM
> Environment: AIX 5.3, JDK 1.5 (last fix), XALAN 2.7.0
> Reporter: Christophe DUVAL
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
