It seems apparent that this would indicate a memory issue, though my server is configured to use what I would assume to be abundant amounts of RAM, and as this error is not particularly verbose, I want to know how I can look into validation;
Is this error just a recognition of it taking absurd amounts of time to complete tasks, or is there some server functionality that is lost because of this, that may explicitly require more than what is available, and therefore is not operating at all?
Essentially, how can I determine if this error is signifying a loss in productivity, or a loss of functionality?
Native code is stored in a memory area called code cache, if the area is too small the JVM will disable its just in time compiler, which can have an impact to your jiras performance
see also https://confluence.atlassian.com/jirakb/full-codecache-causes-jira-server-to-crash-or-perform-slowly-314447083.html and https://confluence.atlassian.com/jirakb/health-check-jvm-code-cache-976778141.html
Cheers
Kurt
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.