On 18/09/2013 09:05, Mark Thomas wrote:
> On 18/09/2013 01:42, jieryn wrote:
>> I'm trying out the new Apache Tomcat 8.0.0-RC2 with some existing web
>> applications that work fine under Apache Tomcat 8.0.0-RC1.
>>
>> I am now seeing literally thousands of warning messages at start up time:
>>
>> 17-Sep-2013 20:19:40.346 WARNING [hostname-startStop-1]
>> org.apache.catalina.webresources.Cache.getResource Unable to add the
>> resource at [{0}] to the cache because there was insufficient free
>> space available after evicting expired cache entries - consider
>> increasing the maximum size of the cache
>>
>> (Note that the [{0}] is the actual text, which suggests a secondary problem.)
>
> I'll fix that.
>
>> Are these messages the result of the Context configuration elements
>> cacheMaxSize, cacheObjectsMaxSize, cacheTTL, and cachingAllowed?
>
> Yes.
>
>> Would it be better to not omit these messages at catalina start up if they
>> are for static resources which have been requested by clients?
>
> No. The cache is used for any web application resource. I suspect the
> problem is that it is currently caching things that shouldn't be cached
> such as class files. I'll take a look.
I've just tried 8.0.0-RC2 with Jira (as an example of a fairly large app
that I know should work without any external plumbing). I've fixed the
broken message and fixed a TODO for excluding some resources from the
cache. Anything loaded by the class loader is now excluded as the class
loader has its own cache (which itself excludes classes).
Those fixes will be in the next RC that hopefully will be out rather
sooner than RC2 was but that depends on the problems folks find and how
long they take to fix.
> Note that apart from filling the logs, there shouldn't be any problem.
I didn't see anything to change this assessment.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
