JSM Data Center: Groovy script action of Assets Automation failed with error 'The request object has been recycled and is no longer associated with this facade' after upgrading to JSM 5.12.12 or above
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
After upgrading JSM, the Groovy script action of Assets automation that used to work fine failed with the error 'The request object has been recycled and is no longer associated with this facade' in the log
Environment
Jira Service Management (JSM) Data Center 5.12.12 and above
Diagnosis
The assets automation action, which worked properly up until JSM Data Center version 5.12.12, encountered a failure, and the related message appeared in the atlassian-jira.log.
1
The request object has been recycled and is no longer associated with this facadeCause
A new change in Apache Tomcat since Apache Tomcat version 9.0.90 is discarding facade objects by default: Tomcat changelog. JSM Data Center version 5.12.12 which uses Apache Tomcat version 9.0.91 has since then include a default start-up property to counter this change. The property looks like this.
1
-Dorg.apache.catalina.connector.RECYCLE_FACADES=falseSolution
Configure the startup property above according to Setting properties and options on startup and restart Jira.
Was this helpful?