Jira is logging multiple cache flushes in the application logs

Atlassian Knowledge Base

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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


The following INFO messages can be seen in the atlassian-jira.log regarding specific caches being flushed. Example:

2021-11-04 15:08:41,001-0300 http-nio-8080-exec-18 INFO      [c.a.c.e.c.a.j.i.f.l.column.DefaultColumnLayoutManager.filterColumnLayoutCache] Cache com.atlassian.jira.issue.fields.layout.column.DefaultColumnLayoutManager.filterColumnLayoutCache was flushed
2021-11-04 15:08:41,001-0300 http-nio-8080-exec-18 INFO      [c.a.c.e.c.a.j.i.f.screen.CachingFieldScreenStore.allScreensCache] Cache com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.allScreensCache was flushed
2021-11-04 15:08:41,001-0300 http-nio-8080-exec-18 INFO      [c.a.c.e.c.a.j.i.f.screen.CachingFieldScreenStore.fieldScreenCache] Cache com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.fieldScreenCache was flushed


Jira 8.19.0 and later


This is expected behavior and will not cause any problems or concerns.

Starting with Jira 8.19.0, Jira will be deployed with a new logging level enabled by default, as described in the following feature request:  JRASERVER-70298 - Getting issue details... STATUS

This is useful when troubleshooting issues with Jira and to determine what caused a specific cache to be flushed. During the Jira startup you will see lots of these messages as it's expected behavior that several Jira caches are populated and flushed for the first time.

How to disable this feature

To disable logging on cache flushes, please follow these steps:

  1. Open the log4j.properties file (located in the Jira application installation directory).
  2. Change the line below from INFO to OFF. Example:

    log4j.logger.com.atlassian.cache.event = OFF, filelog
  3. Save the file and restart the node for the changes to take effect.

Last modified on Nov 4, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.