Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-70281

JVM Code Cache memory check is failing in ATST version 1.23.1

    XMLWordPrintable

    Details

      Description

      Issue Summary

      Users that have updated to the latest ATST version available in the marketplace, that was 1.23.1, may receive a failed health check regarding JVM Code Cache memory.

      The failed health check error shows up regardless of the Code Cache memory size specified in the JVM parameters.

      Steps to Reproduce

      This problem has multiple causes, so isn't directly reproducible.

      Expected Results

      The troubleshooting tools only show up an error in Code Cache memory size when there's an actual problem

      Actual Results

      An error is displayed even though the code cache size is adequate

      Workaround

      • The actual ReservedCodeCacheSize may still be too small. Increase it by following Full Code Cache Size Causes Jira Server to Crash or Perform Slowly article.
      • Then, clear catalina.out log file under <JIRA_INSTALL>/logs directory because the health check may be responding to outdated messages in. Here is the sample log:
        ...
        ...
        Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled.
        Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=
        CodeCache: size=524288Kb used=503421Kb max_used=518081Kb free=20866Kb
        
      • Restart Jira node(s)

      If there is still a health check warning although ReserveCodeCacheSize is increased, raise a ticket to Atlassian Support for further investigation.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              rbaldasso Rodrigo Baldasso
              Votes:
              17 Vote for this issue
              Watchers:
              52 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: