Specific User is getting "Data cannot be retrieved due to an unexpected error" when using JIRA Issue Macro

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

When trying to use JIRA Issue macro, a specific user is getting a "Data cannot be retrieved due to an unexpected error" in the Confluence UI.

The following error is then thrown in Confluence and JIRA logs:

1 2 3 4 5 6 7 8 9 10 11 12 2016-04-12 15:56:36,549 DEBUG [http-nio-8090-exec-47] [extra.jira.helper.JiraExceptionHelper] throwMacroExecutionException Macro execution exception: -- referer: http://localhost:8090/pages/editpage.action?pageId=23823660 | url: /pages/viewpage.action | userName: user1 | action: viewpage | page: 23823660 java.lang.RuntimeException: Internal Server Error at com.atlassian.confluence.extra.jira.util.JiraUtil.checkForErrors(JiraUtil.java:78) at com.atlassian.confluence.extra.jira.JiraAppLinkResponseHandler.handle(JiraAppLinkResponseHandler.java:35) at com.atlassian.applinks.core.auth.oauth.OAuthApplinksResponseHandler$1.handle(OAuthApplinksResponseHandler.java:127) at com.atlassian.applinks.core.auth.oauth.OAuthApplinksResponseHandler.handle(OAuthApplinksResponseHandler.java:85) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:166) at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:361) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:84) ...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 2016-04-12 15:56:36,549 http-bio-443-exec-202 ERROR anonymous 956x844064x1 - 10.0.0.254 /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml [oauth.serviceprovider.internal.AuthenticatorImpl] Failed to validate OAuth message.com.atlassian.cache.CacheException: com.atlassian.oauth.serviceprovider.InvalidTokenException: Token '2MRQAkCrxCghkIDV7O9BV086af7eLlzd' is an access token, but has no user associated with it at com.atlassian.cache.memory.DelegatingCache$DelegatingLoadingCache.get(DelegatingCache.java:306) at com.atlassian.jira.oauth.serviceprovider.CachingServiceProviderTokenStore.get(CachingServiceProviderTokenStore.java:79) at sun.reflect.GeneratedMethodAccessor1540.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62) ... Caused by: com.atlassian.oauth.serviceprovider.InvalidTokenException: Token '2MRQAkCrxCghkIDV7O9BV086af7eLlzd' is an access token, but has no user associated with it at com.atlassian.jira.oauth.serviceprovider.OfBizServiceProviderTokenStore.createTokenFromGV(OfBizServiceProviderTokenStore.java:387) at com.atlassian.jira.oauth.serviceprovider.OfBizServiceProviderTokenStore.get(OfBizServiceProviderTokenStore.java:130) at com.atlassian.jira.oauth.serviceprovider.CachingServiceProviderTokenStore$TokenCacheLoader.load(CachingServiceProviderTokenStore.java:170) at com.atlassian.jira.oauth.serviceprovider.CachingServiceProviderTokenStore$TokenCacheLoader.load(CachingServiceProviderTokenStore.java:165) at com.atlassian.cache.memory.MemoryCacheManager$3$1.load(MemoryCacheManager.java:130) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)

Diagnosis

Environment

Diagnostic Steps

To ensure that the OAuth Access Tokens are indeed valid, please login to both Confluence and JIRA with the affected user's credential and then do the following to revoke the access of that particular user so that his token would be regenerated:

  • In Confluence

    1. Navigate to User Profile page >> Settings >> View OAuth Access Tokens

    2. Click Revoke Access for the listed JIRA application.

  • In JIRA

    1. Navigate to User Profile page >> Tools >> View OAuth Access Tokens

    2. Click Revoke Access for the listed Confluence application.

Once you've done this, then please try to replicate the issue again and check if indeed the issue recurs. Should indeed the issue recurs, please proceed to the Workaround section of this KB.

Cause

The OAuth token for this particular user had been corrupted.

Solution

Workaround

As the token had been corrupted we'd then need to recreate the Application Links to ensure that there is no misconfiguration on the Application Link configuration.

For more information, please refer to our Application Links Troubleshooting.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.