https://issues.apache.org/bugzilla/show_bug.cgi?id=53081
vladk <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from vladk <[email protected]> --- 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: [email protected] For additional commands, e-mail: [email protected]
