Creating an issue in Jira throws the error "Temporary attachment not found. Session may have timed out before submitting the form."

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

The following error is displayed when creating a Jira issue: "Temporary attachment not found. Session may have timed out before submitting the form.".

Environment

Jira

Diagnosis

  • Issue gets created successfully even if the error message is displayed.
  • ScriptRunner app is installed in the Jira instance.
  • Generating a HAR file and analyzing web requests shows the following result:
    • QuickCreateIssue.jspa?decorator=none request timeout after 60 seconds:

    • Error can also be seen on the HAR response:

      |


  • In the catalina.out log, there are some stuck threads related to the Creation issue action involving ScriptRunner third-party app:

    catalina.out
    28-Mar-2022 14:47:21.535 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-38] (id=[170955]) has been active for [129,264] milliseconds (since [3/28/22 2:45 PM]) to serve the same request for [https://xxxxx.com/secure/QuickCreateIssue.jspa?decorator=none] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck.
    	java.lang.Throwable
    		at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:231)
    		at com.atlassian.jira.logging.JiraHomeAppender.doAppend(JiraHomeAppender.java:206)
    		at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:69)
    ...
    	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    		at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
    		at com.sun.proxy.$Proxy3114.doWorkflowAction(Unknown Source)
    		at com.atlassian.jira.workflow.WorkflowManager$doWorkflowAction$1.call(Unknown Source)
    		at com.onresolve.scriptrunner.canned.jira.utils.WorkflowUtil.actionIssueWithFeedBack(WorkflowUtil.groovy:348)
    		at com.onresolve.scriptrunner.canned.jira.utils.WorkflowUtil$actionIssueWithFeedBack$1.call(Unknown Source)
    		at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.FasttrackTransition.execute(FasttrackTransition.groovy:133)
    		at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.FasttrackTransition$execute$0.callCurrent(Unknown Source)
    		at com.onresolve.scriptrunner.canned.jira.workflow.AbstractWorkflowCannedScript.execute(AbstractWorkflowCannedScript.groovy:23)
    		at com.onresolve.scriptrunner.canned.jira.workflow.AbstractWorkflowCannedScript$execute.call(Unknown Source)
    		at com.onresolve.scriptrunner.jira.workflow.AbstractScriptWorkflowFunction$_run_closure2.doCall(AbstractScriptWorkflowFunction.groovy:89)
    		at com.onresolve.scriptrunner.jira.workflow.AbstractScriptWorkflowFunction$_run_closure2.doCall(AbstractScriptWorkflowFunction.groovy)
    		at jdk.internal.reflect.GeneratedMethodAccessor5108.invoke(Unknown Source)
    		at java.base@11.0.11/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    		at java.base@11.0.11/java.lang.reflect.Method.invoke(Unknown Source)
    		at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:101)
    		at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:323)
    		at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:263)
    		at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1041)
    		at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:37)
    		at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
    		at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:52)
    		at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
    		at com.onresolve.scriptrunner.runner.diag.DiagnosticsManagerImpl$DiagnosticsExecutionHandlerImpl$_execute_closure1.doCall(DiagnosticsManagerImpl.groovy:370)
    		at com.onresolve.scriptrunner.runner.diag.DiagnosticsManagerImpl$DiagnosticsExecutionHandlerImpl$_execute_closure1.doCall(DiagnosticsManagerImpl.groovy)
    		at jdk.internal.reflect.GeneratedMethodAccessor4867.invoke(Unknown Source)
    		at java.base@11.0.11/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    		at java.base@11.0.11/java.lang.reflect.Method.invoke(Unknown Source)
    		at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:101)

Cause

The post-function Fast-track Transition an Issue from ScriptRunner is being used.

Solution

There are two approaches that can be taken:

  1. Reach out to ScriptRunner vendor, as their support team should be better equipped to fix this issue.
  2. Disable ScriptRunner app.

Last modified on Jul 29, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.