Assets Automation Rule Fails after Upgrading Jira Data Center.
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Assets Automation rules that execute a Groovy script encounter errors following the Jira upgrade. The errors noted in the Atlassian-jira.log during the execution of the Asset Automation rules are detailed below.
2024-11-08 11:47:02,718+0100 insight-event-8 ERROR admin [insightAutomationCreateMAEintrittIssue]
insightAutomationCreateMAEintrittIssue HR-123456 :: : Error: The request object has been recycled and is no longer associated with this facadeEnvironment
Jira Service Management version 5.12.12 or higher.
Diagnosis
Go to the page ⚙ > System > System Info, scroll to the section JVM Input Arguments and check if the JVM parameters below are listed in that section:
-Dorg.apache.catalina.connector.RECYCLE_FACADES=falseIf this argument is missing, you may proceed to the Solution section to address the issue.
Cause
There are several changes introduced in Tomcat version 9.0.90, where the system property org.apache.catalina.connector.RECYCLE_FACADES will now default to true if not specified. This modification will subsequently set the default value for the discardFacades connector attribute, resulting in facade objects being discarded by default. To address this change, starting from Jira version 5.12.12, a new property has been introduced. The issue arises because, following the upgrade, this new property, which is set by default in Jira, may be missing.
-Dorg.apache.catalina.connector.RECYCLE_FACADES=false Jira admins performing system updates or upgrades might rollover changes included by default in these files if they replace the file without manually adding their customisations. If these new arguments are missing, the symptoms described in this article will be observed.
Solution
To solve the problem add back the JVM Startup parameter listed below by following the steps described in how to set Java properties and options on startup for Jira.
-Dorg.apache.catalina.connector.RECYCLE_FACADES=false 
It's necessary to make this change to each Jira node in case of a cluster and restart them to make the changes take effect.