Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Seimei Kurosawa
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 11, 2019

Hi

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.

Regards,

 

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 12, 2019

Hi,

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.

Regards,

Andy

Seimei Kurosawa
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 13, 2019

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.

 

Regards,

Seimei

Harold Wong
Contributor
July 14, 2019

I too am experiencing this...

arielbarros September 9, 2020

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

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 9, 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.

Andy

Suggest an answer

Log in or Sign up to answer