Bulk archive assets action fails
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
After upgrading JSM, it is not possible to bulk archive Assets objects. When executing the bulk archive functionality in Assets for multiple objects the The request object has been recycled and is no longer associated with this facade ERROR is thrown out in the atlassian-jira.log and the bulk archive action fail.
Environment
Jira Service Management (JSM) Data Center 5.12.12 and above
Diagnosis
The bulk archive assets action, which worked properly up until JSM Data Center version 5.12.12, encountered a failure, and the related ERROR message appeared in the atlassian-jira.log:
insight-InsightBulkArchiveRestoreThreadGroup-worker-thread-3 ERROR [c.r.j.p.i.s.core.archiving.BulkArchiveHandlerImpl] Error while executing bulk archive for a batch
java.lang.IllegalStateException: 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.
-Dorg.apache.catalina.connector.RECYCLE_FACADES=falseSolution
Configure the startup property above according to Setting properties and options on startup and restart Jira.