Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-39368

Excessive Log messages insufficient free space available after evicting expired cache entries

    Details

    • Symptom Severity:
      Major
    • UIS:
      10
    • Support reference count:
      23
    • Occurrence Factor:
      10%

      Description

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      In Confluence 5.8.x on Tomcat 8, clients are receiving messages as follows:

      22-Sep-2015 16:29:05.107 WARNING [http-nio-8443-exec-2] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/includes/css/blogpost-move-dialog.css] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
      22-Sep-2015 16:29:05.108 WARNING [http-nio-8443-exec-2] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/images/icons/savas_16.gif] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
      22-Sep-2015 16:29:05.109 WARNING [http-nio-8443-exec-2] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/images/icons/emoticons/lightbulb.png] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
      

      This appears to be a widely known issue within Tomcat 8, not sure how clients can easily adjust cache, or if this is a concern as these are only WARNING messages, but it does cause a great deal of concern from clients.

      Workaround:

      Suppress cache log warnings

      To reduce the noise level of these WARNING messages:

      1. Go to Administration > Logging and Profiling
      2. Set the logging level to ERROR for org.apache.catalina.webresources.Cache
      3. If the class does not exist, add the class to the list of packages to be logged and set the logging level to ERROR

      Not sure if these are truly harmless, or if this is indicative of a problem with Tomcat 8 and Confluence.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                11 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Last commented:
                  21 weeks, 4 days ago