On 07/10/2016 21:38, Martin Grigorov wrote: > Hi Mark, > > On Fri, Oct 7, 2016 at 6:39 PM, Mark Thomas <ma...@apache.org> wrote: > >> On 07/10/2016 15:51, Mark Thomas wrote: >>> On 07/10/2016 14:50, Martin Grigorov wrote: >>>> On Thu, Oct 6, 2016 at 10:33 PM, Mark Thomas <ma...@apache.org> wrote: >>>> >>>>> The proposed Apache Tomcat 8.5.6 release is now available for voting. >>>>> >>>>> The major changes compared to the 8.5.5 release are: >>>>> >>>>> - Refactoring the non-container thread Async complete()/dispatch() >>>>> handling to remove the possibility of deadlock >>>>> >>>>> - Update the packaged version of the Tomcat Native Library to >>>>> 1.2.10 to pick up the latest Windows binaries built with >>>>> OpenSSL 1.0.2j >>>>> >>>>> - Improved UTF-8 handling for the RewriteValve >>>>> >>>>> >>>>> It can be obtained from: >>>>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.6/ >>>>> The Maven staging repo is: >>>>> https://repository.apache.org/content/repositories/ >> orgapachetomcat-1097/ >>>>> The svn tag is: >>>>> http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_6/ >>>>> >>>>> The proposed 8.5.6 release is: >>>>> [ ] Broken - do not release >>>>> [ ] Alpha - go ahead and release as 8.5.6 >>>>> [ ] Beta - go ahead and release as 8.5.6 >>>>> [ X ] Stable - go ahead and release as 8.5.6 >>>>> >>>> >>>> The only thing that bothers me a bit is that I have a lot of those >> during >>>> start: >>>> >>>> 07-Oct-2016 15:27:58.342 WARNING [RMI TCP Connection(4)-127.0.0.1] >>>> org.apache.catalina.webresources.Cache.getResource Unable to add the >>>> resource at [/WEB-INF/lib/lucene-memory-5.5.2.jar] to the cache because >>>> there was insufficient free space available after evicting expired cache >>>> entries - consider increasing the maximum size of the cache >>> >>> I suspect that this is the cause: >>> >>> https://bz.apache.org/bugzilla/show_bug.cgi?id=60146 >>> >>> We might need to tweak the caching algorithm and/or config. >> >> I haven't been able to reproduce this with a simple test. Can you do >> some debugging and see what code path is triggering the loading of the >> JAR files this way. >> > > Here is the stacktrace: http://imgur.com/a/ioRY4 > I use the sources of the voted 8.5.6, not the latest 8.5.x.
Thanks. I think I see what is happening now. The Cache entry size is calculated based on file size regardless of whether the content of the entry is cached or not. What isn't clear is why you saw this with 8.5.6 but not earlier releases. I think the correct solution here is to make JAR files in WEB-INF/lib non-cacheable. I'll try that for the next release Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
