Confluence cannot move any thing in Calendar with Jira Issue After Upgrade from 7.19.4 to 8.5.3

quannd December 3, 2023

After Upgrade from 7.19.4 to 8.5.3 My Confluence have problem with Team Calendar:

Cannot move any thing in Calendar with Jira Issue:

Error(s) occurred.

  • com.atlassian.applinks.api.CredentialsRequiredException: You do not have an authorized access token for the remote resource.

Below is image & log for detail problem.

Please help me to recover this problem.

Thanks & best regard.

PS: I had applied the renewal license for Team Calendar with latest version.

Link Application between Confluence & Jira is deleted & recreated successful.

And server is restart too.

application link error.png

2023-12-04 09:21:42,346 WARN [http-nio-8090-exec-6] [atlassian.applinks.core.DefaultApplicationLinkService] retrieveApplicationLink Couldn't find type id for application link with id 74899f97-6765-3d98-b0ec-e893179a1a1c. Link is corrupted
at java.base/java.lang.Thread.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:390)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.StuckThreadDetectionValve.invoke(StuckThreadDetectionValve.java:185)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:670)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:765)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:32)
at com.atlassian.confluence.web.filter.DebugFilter.doFilter(DebugFilter.java:63)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.confluence.impl.webapp.ConfluenceHttpHeaderSecurityFilter.doFilter(ConfluenceHttpHeaderSecurityFilter.java:48)
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:129)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:32)
at com.atlassian.confluence.web.filter.DropIfNotSetupFilter.doFilter(DropIfNotSetupFilter.java:32)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.confluence.internal.diagnostics.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:42)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.confluence.internal.diagnostics.ipd.http.IpdHttpMonitoringFilter.doFilter(IpdHttpMonitoringFilter.java:35)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at com.atlassian.confluence.servlet.FourOhFourErrorLoggingFilter.doFilter(FourOhFourErrorLoggingFilter.java:64)
..................................................
java.lang.IllegalStateException: Failed to obtain client registration lock, cannot update potential client 2e7b3cdf-4e09-3559-8605-946a7b6357a6
-- url: /rest/mywork/1/client | userName: anonymous | traceId: 8cd49a1ab6ea04ce
2023-12-04 09:21:41,104 ERROR [http-nio-8090-exec-10] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from REST resource
-- traceId: 601513e40b93fe9d
2023-12-04 09:21:35,150 WARN [http-nio-8090-exec-8] [atlassian.applinks.core.DefaultApplicationLinkService] retrieveApplicationLink Couldn't find type id for application link with id 74899f97-6765-3d98-b0ec-e893179a1a1c. Link is corrupted
-- url: /rest/gadgets/1.0/g/messagebundle/und/gadget.common%2Cgadget.activity.stream | userName: anonymous | traceId: adb21e0362302dc5
2023-12-04 09:21:33,736 WARN [myWorkClientChecker:thread-1] [atlassian.applinks.core.DefaultApplicationLinkService] retrieveApplicationLink Couldn't find type id for application link with id 74899f97-6765-3d98-b0ec-e893179a1a1c. Link is corrupted
2023-12-04 09:21:32,659 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve

 

3 answers

1 vote
Marc - Devoteam
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.
December 4, 2023

Hi @quannd 

I think you might be running in to the issue as explained in the following Atlassian Kb article.

applink-corrupted-error-in-confluence 

I hope this article will solve your issue.

quannd December 4, 2023

@Marc - Devoteam Thank you!!!

quannd December 4, 2023

Thank you for your suggest!

I had fixed this Issue AppLink Corrupted Error in Confluence | Confluence | Atlassian Documentation

Now there is no error about Application link in log but the problem of Calendar is still the same. 

quannd December 5, 2023

@Marc - Devoteam Thank you again! I 've tried it & still be in the same state with nothing happen :(

So I let this information here and hope it will be useful to you.

0 votes
quannd December 5, 2023

There is not error but it's disabled in some feature!!!

I can still edit Issue Date & Info in Detail but cannot only Drag & Drop in Schedule!

Is that an restrict of Update Version in Team Calendar?

If that's correct, this restrict is a little inconvenient for almost user, I think.

At this time, I cannot raise this Issue because of restrict support.

When the support Team is available I hope there will be clearly resolution.

Thanks anyway ^^

 

pasted-2023.12.06-10.39.52.png

0 votes
quannd December 4, 2023

Error(s) occurred.

  • com.atlassian.applinks.api.CredentialsRequiredException: You do not have an authorized access token for the remote resource.

I allow authorized access successfully & there is no more alert of above error message but nothing is happen, the problem is still remain.

Calendar.png

Marc - Devoteam
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.
December 4, 2023

Hi @quannd 

Coudl you try this work around.

JICAL-40 | Plugin will not ask to authenticate the connection to Jira if token is not present.

The workaround is as follows:

  1. Create a new page (this can be deleted later)
  2. Insert a Jira Issues macro there

The problem occurs because Jira does not request a new token for authentication. The Jira Issue macro creates a new token and the calendar should work.

See also KB article: jira-events-do-not-load-in-team-calendars 

quannd December 5, 2023

@Marc - Devoteam Thanks you! I 'll try it.

quannd December 5, 2023

@Marc Koppelaar Thank you again! I 've tried it & still be in the same state with nothing happen :(

So I let this information here and hope it will be useful to you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.3
TAGS
AUG Leaders

Atlassian Community Events