https://issues.apache.org/bugzilla/show_bug.cgi?id=53081
vladk <vladk....@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vladk....@gmail.com
--- Comment #3 from vladk <vladk....@gmail.com> ---
We are observing significant performance degradation caused by this fix. In our
case, the DocumentBuilderFactory.newInstance() method looks for class path
resources. Before that fix the WebAppClassloader cached resources it had found
and only the first call was slow. Now it scans jars on the classpath in each
call and reading a big signed jar takes quite long.
We should be able to solve our problem by using
javax.xml.parsers.DocumentBuilderFactory system property, but this change in
the WebAppClassloader can cause performance degradation at other places.
Is there any better way to solve the mentioned OutOfMemoryError?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
