On 01/09/17 11:25, Johan Compagner wrote:


> We tested it and the winner is:
> <Listener
> className="org.apache.catalina.core.JreMemoryLeakPreventionListener"
>     urlCacheProtection="false" />
> i had my bets on the xmlParsingProtection but that wasn't it...

When I took a look through the options, urlCacheProtection looked to be
the most likely.

Be aware you may end up with some file locking / memory leak issues on
web application reload with that disabled. The simplest solution is to
restart Tomcat as part of the redeployment process.

As of Java 9, there is a new API that allows more selective disabling of
caching so we'll be able to disable it just for JARs when running on
Java 9. Generally, we got a whole bunch of memory leak issues fixed for
Java 9. Oracle were very receptive to fixing the bugs we reported. See
[1] for more info.

Which reminds me, we need to update the listener to use this new API
when running on Java 9.


[1] https://github.com/markt-asf/memory-leaks

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to