Excessive log messages in Jira about insufficient free space available after evicting expired cache entries
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Jira logs contain an excessive number of messages stating "there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache".
Environment
Jira Data Center 8.x and above.
Diagnosis
Many occurrences of the following warning message are observed in the atlassian-jira.log:
1
2
3
27-Jan-2024 10:03:55.003 WARNING [Modification Check:thread-1] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at
[/secure/johnson-page/johnson-error-page.jsp] to the cache for web application [/tracker03] because there was insufficient free space available
after evicting expired cache entries - consider increasing the maximum size of the cacheCause
The cause is a new implementation of Warning messages in Tomcat starting version 8, whereas Tomcat 7 doesn't log these.
1
2
3
4
5
6
if (newSize > maxSize) {
// Unable to create sufficient space for this resource
// Remove it from the cache
removeCacheEntry(path);
log.warn(sm.getString("cache.addFail", path));
} Solution
Though the warning messages are not known to cause any adverse performance impact on Jira, there are two possible options to suppress them:
Option 1 - Suppress cache log warnings:
Go to Jira Administration > System > Logging and Profiling
Set the logging level to ERROR for the class
org.apache.catalina.webresources.CacheIf the class does not exist, add the class to the list of packages to be logged and set the logging level to ERROR
Option 2 - Adjust the cache size:
Add the lines below to <JIRA_INSTALL>/conf/server.xml file in the Context section:
1
2
3
4
<Resources
cachingAllowed="true"
cacheMaxSize="100000"
/> Note: Please be aware that implementing these changes may result in the application utilizing slightly more RAM. Specifically, this will involve increasing the cacheMaxSize to 100 MB from its default value of 10 MB.
Was this helpful?