JVM Code Cache Health Check requires non existent ATST version?

Christopher Gronde January 23, 2020

We have upgraded our test environment to Jira 8.6.1 and in the release notes it states there is a new JVM Code Cache Health Check.

https://confluence.atlassian.com/jirasoftware/jira-software-8-6-x-release-notes-978220007.html?_ga=2.92601369.523903709.1579718537-1672574166.1564757447#JiraSoftware8.6.xreleasenotes-jvm

It also states in order to see this new health check you must upgrade your Atlassian Troubleshooting and Support Tool to version 1.30.0.

According to the Atlassian Marketplace the most recent version of ATST is 1.23.1 for Datacenter and 1.21.3 for Jira Server. 

https://marketplace.atlassian.com/apps/1217696/troubleshooting-and-support-jira/version-history

Sooooo where is version 1.30.0?  Or does it not exist and the release notes for 8.6.1 talk about a health check that doesn't exist yet?

1 answer

0 votes
Adrian Stephen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 23, 2020

Hi @Christopher Gronde 

There seems to be an error with the version on 

There are two versions of 1.23.1. 

Go to the manage apps page on your Jira Instance and confirm that there is no update available for ATST. If there is, update it. I might get updated to another version of 1.23.1 


Once you have done that, you should see the Code Cache Memory health check at the Troubleshooting and support tools page under the Java Virtual Machine section. 

Adrian Stephen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 23, 2020

Screenshot 2020-01-23 at 11.29.57 PM.png

Christopher Gronde January 23, 2020

The problem is that our server instance is not allowed to connect directly to Atlassian Marketplace, so I can't update through the manage Apps page.  We can only download from Marketplace and manually upload to our server instance.  

Christopher Gronde January 23, 2020

Also this doesn't answer why the release notes say 1.30?

Adrian Stephen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 23, 2020

Hi @Christopher Gronde 

Can you go to the manage apps page in Jira, expand Atlassian Troubleshooting and Support Tools > expand the modules ( you should see 52 of 52 modules enabled ) and search for "codecache". Are you able to see this module? 

Screenshot 2020-01-24 at 1.03.02 AM.pngScreenshot 2020-01-24 at 1.03.09 AM.png

 

Regarding your question:

Also this doesn't answer why the release notes say 1.30?

I believe that this might be an error/typo on our end because there are two versions of 1.23.1 at https://marketplace.atlassian.com/apps/1217696/troubleshooting-and-support-jira/version-history and I'm still checking this internally. 

If you do not see the module healthcheck.codecache.name, could you try downloading and uploading the 1.23.1 version for Jira Data Center 7.4.3 - 8.6.1 from https://marketplace.atlassian.com/apps/1217696/troubleshooting-and-support-jira/version-history because this feature works on my end as the screenshot above. 

Tom Lister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 28, 2020

FYI

we are running 1.23.1 for Data Centre and have definitely started getting the Code Cache warnings since we updated.

image.png

NCATS LAB February 5, 2020

We are getting errors since the update, too. I have increased the Code Cache size, but still getting errors. Atlassian has no guidance on Code Cache size (that I can find). I don't want to keep increasing it - it is already larger than I would expect is needed.

Suggest an answer

Log in or Sign up to answer