java.util.concurrent.CancellationException

Atlassian JIRA | Ahmad Danial | 3 years ago
  1. 0

    h5. Overview The Issue Link is not updated when the one of the original macros were removed from the page and throwing some error message on the Confluence UI h5. Steps to Reproduce * Create a Blank Page from a brand new Confluence installation !jira_issue_1.JPG|thumbnail! * Insert two JIRA Issues Macro as per the following screen shot !jira_issue_2.JPG|thumbnail! * Confirm on the amount of JIRA links (In this case 2 links) !jira_issue_3.JPG|thumbnail! * After that, we edited the page and removed one of links. After saving the page, the links were still showing 2 links and after clicking the links button, we get the following error on the UI (and the links is showing 0 JIRA Links) !jira_issue_4.JPG|thumbnail! * After refreshing the page, it will show the wrong Issue Link count again (2 Issue Link) in this example !jira_issue_5.JPG|thumbnail! Checking from the {{atlassian-confluence.log}}, we can see the following exception below: {code} 2014-05-24 20:30:17,059 WARN [http-bio-8551-exec-6] [metadata.jira.helper.JiraMetadataErrorHelper] printError One or more JIRA instances could not be reached. -- url: /conf_551/rest/jira-metadata/1.0/metadata | userName: admin | referer: http://localhost:8551/conf_551/display/ds/JIRA+Issues+Macro+Testing java.util.concurrent.CancellationException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:220) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.atlassian.confluence.plugins.metadata.jira.service.helper.FutureMetadataHelper.processFutures(FutureMetadataHelper.java:58) at com.atlassian.confluence.plugins.metadata.jira.service.helper.FutureMetadataHelper.process(FutureMetadataHelper.java:42) at com.atlassian.confluence.plugins.metadata.jira.service.JiraMetadataService.getMetadata(JiraMetadataService.java:99) at com.atlassian.confluence.plugins.metadata.jira.rest.JiraMetadataResource.getMetadata(JiraMetadataResource.java:25) ... {code} h5. Expected Behaviour The Issue Link count should reflect the updated amount of JIRA Issues Macro link after the page is updated (when any JIRA Issues Macro is / are removed) h5. Environment JIRA 6.2.5 + Confluence 5.5.1 + JIRA Agile 6.3.13.1

    Atlassian JIRA | 3 years ago | Ahmad Danial
    java.util.concurrent.CancellationException
  2. 0

    java ExecutorService how to handle timeouts

    Stack Overflow | 2 years ago | roymustang86
    java.util.concurrent.CancellationException
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    When I run KMS unit tests in debug mode, the debugger breaks at the following point (within several different tests), even though I have no breakpoints set, and then I have to hit continue to allow the junit tests to proceed, and when I hit continue I noticed the below exception stack that includes ResubmittingScheduledThreadPoolExecutor.afterExecute. I've seen this kind of problem before when an independent thread does not have a surrounding try/catch, and it throws an exception (e.g. a runtime exception) and there is no parent to catch the exception. The easiest fix is to put a try/catch (Exception e) around the whole method body, and do something (e.g. log amd email a msg, execute recovery code,...as approp) when the exception occurs. {code} ThreadPoolExecutor.runTask(...) { ... workerDone(this) ... } {code} This this exception appears in the console log: {code} Exception in thread "pool-20-thread-1" java.util.concurrent.CancellationException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:220) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.kuali.kits.kms.scheduler.ResubmittingScheduledThreadPoolExecutor.afterExecute(ResubmittingScheduledThreadPoolExecutor.java:81) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {code}

    Kuali JIRA | 4 years ago | Mike Riley
    java.util.concurrent.CancellationException
  5. 0

    When I run KMS unit tests in debug mode, the debugger breaks at the following point (within several different tests), even though I have no breakpoints set, and then I have to hit continue to allow the junit tests to proceed, and when I hit continue I noticed the below exception stack that includes ResubmittingScheduledThreadPoolExecutor.afterExecute. I've seen this kind of problem before when an independent thread does not have a surrounding try/catch, and it throws an exception (e.g. a runtime exception) and there is no parent to catch the exception. The easiest fix is to put a try/catch (Exception e) around the whole method body, and do something (e.g. log amd email a msg, execute recovery code,...as approp) when the exception occurs. {code} ThreadPoolExecutor.runTask(...) { ... workerDone(this) ... } {code} This this exception appears in the console log: {code} Exception in thread "pool-20-thread-1" java.util.concurrent.CancellationException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:220) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.kuali.kits.kms.scheduler.ResubmittingScheduledThreadPoolExecutor.afterExecute(ResubmittingScheduledThreadPoolExecutor.java:81) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {code}

    Kuali JIRA | 4 years ago | Mike Riley
    java.util.concurrent.CancellationException

  1. Saravana Kumar Chinnaraj 2 times, last 8 months ago
  2. ashish.sadhwani 1 times, last 8 months ago
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.util.concurrent.CancellationException

    No message provided

    at java.util.concurrent.FutureTask$Sync.innerGet()
  2. Java RT
    FutureTask.get
    1. java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:220)
    2. java.util.concurrent.FutureTask.get(FutureTask.java:83)
    2 frames
  3. com.atlassian.confluence
    JiraMetadataResource.getMetadata
    1. com.atlassian.confluence.plugins.metadata.jira.service.helper.FutureMetadataHelper.processFutures(FutureMetadataHelper.java:58)
    2. com.atlassian.confluence.plugins.metadata.jira.service.helper.FutureMetadataHelper.process(FutureMetadataHelper.java:42)
    3. com.atlassian.confluence.plugins.metadata.jira.service.JiraMetadataService.getMetadata(JiraMetadataService.java:99)
    4. com.atlassian.confluence.plugins.metadata.jira.rest.JiraMetadataResource.getMetadata(JiraMetadataResource.java:25)
    4 frames