Forums

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

Errors after Jira Upgrade from 6.4.7 to 7.0.11

Peter Schneider March 23, 2018

After performing Jira upgrade from 6.4.7 to 7.0.11 (as a first step to finally upgade to 7.8), I cannot access the instance, with a 500 error and Java stack trace:

Technische Details

Verweisnummer des Protokolls: 4ceb5555-ae34-48b7-96e7-2c86cd4cf82d

Ursache

Verweiser-URL: Unknown

java.lang.RuntimeException: javax.servlet.ServletException: java.lang.NoSuchMethodError: com.atlassian.jira.security.JiraAuthenticationContext.getLoggedInUser()Lcom/atlassian/crowd/embedded/api/User;

 

I can provide the full stack trace and also the catalina.out, if necessary.

Thanks for any suggestions,

Peter

1 answer

1 accepted

0 votes
Answer accepted
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2018

It looks to me like you have a plugin that is not updated yet. Try starting JIRA in safe mode and then upgrade the plugin. Or remove the plugin that is still using the old API before starting JIRA.

Peter Schneider March 23, 2018

Thanks, that worked for me. I renamed the installed-plugins folder, then I could access the instance and re-install all licensed plugins with the latest version.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events