https://bz.apache.org/bugzilla/show_bug.cgi?id=68909
--- Comment #8 from Mark Thomas <ma...@apache.org> --- Arguably the this issue isn't a Tomcat issue. This bug is a result of the application using the work-around of setting the system property. That in turn is used due to application and/or library issues loading the correct XML parser. The fix to EncodingDetector is the right one to avoid web application class loader pinning. It appears from comment #2 that the system property is set programmatically in the web application. If that is the case then we may have a workaround for your workaround. If you add org.apache.jasper.compiler.EncodingDetector to the classesToInitialize property of the JreMemoryLeakPreventionListener that should trigger loading of the EncodingDetector before the web application starts and the system property is set. Long term, I'd suggest looking at the application and/or the libraries and trying to fix whatever issues mean you need to set the system property. Whether the above workaround solves the problem or not, I am leaning to resolving this as INVALID since it is caused by setting the system property which isn't appropriate in a web application environment. -- 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
