Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Problem with JVM health check after update to version 8.20

Hi, I faced with health check problem after jira was updated from 8.14 to version 8.20.
I followed the recommendations and set ExplicitGCInvokesConcurrent parameter in
order to fix this issue, but after that jira starts to malfunction every day in
the same time I see growth of cpu and system utilization. Couple day before
I remove this parameter and Jira starts to work much better. How can I fix alert about failed health check and didn't set this parameter because it affect system performance. Maybe I more system investigation, please give me advice

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events