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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why I got Token Error when I tried to run GC collection from Admin?


After I upgraded JIRA 8.2.2 to 8.2.3 by following he security announcement, I become not able to run "Force garbage collection" from the Admin page "System Info".
I keep receiving the error "XSRF Security Token Missing".
I read the suggested documents but looks none of these can help.

This function is very convenient rather than working in Java.

please advice.



1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Jul 12, 2019


Sorry to hear about this error.  I understand that you have upgraded Jira to 8.2.3 and since that time you are unable to use the 'Force Garbage Collection' feature within the system info page in Jira.

I was also able to recreate this problem in my 8.2.3.  As such I created a new bug for this problem in JRASERVER-69609.  Sorry there does not appear to be a work-around for this at this time.  But if one should become available that ticket will likely be updated with the details.  I would watch that issue for additional updates here.



Hi Andy,


Many thanks for following up the issue.

It is good to know you could recreate the case.

My JIRA is still running so that it won't cause an immediate issue.

However, I would hope to receive a solution soon.

I would appreciate it very much if you could find a workaround earlier.




I too am experiencing this...

I have the same problem. I would appreciate if you inform me about the solution as soon as it exists.
Thank you very much!!!

Andy Heinzer Atlassian Team Sep 09, 2020

Hi @arielbarros 

This is a bug that we tracked in JRASERVER-69609.  This was fixed back in 8.3.2 and 8.4.0.  If you happen to be running a Jira Server 8.2.x or before 8.3.2, then you would need to upgrade Jira in order to one of these versions or higher in order to correct this.

Let me know if you happen to be running a newer version where this happens.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,642 views 22 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you