Jama 9.22.1: Slow Batch Update Performance

Published Date: June 16, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® version(s): 9.17.x, 9.22.x
- Cloud/CVC
- Self-hosted
Database: MySQL 8.x

Summary

This article explains how to diagnose and resolve an issue where Batch Update in Jama Connect® takes minutes when updating only a small number of items (for example, 4–7 minutes for 4–7 items). In affected environments, the delay typically appears during the “duplicate documents” stage of the batch update workflow.

The confirmed root cause is a performance issue in the MySQL stored procedure sp_batch_update_duplicate_step_item.

Symptoms

Batch updating a small number of items takes several minutes, even though very large batch updates may perform acceptably.
The Batch Update progress dialog appears stuck on a step such as “creating versions” or similar.
HAR captures show repeated polling to:
- /dwr/call/plaincall/workProgressSvc.getProgressForId.dwr
Application logs show the majority of batch update time in:
- Batch Update: duplicate documents took <large value>s (...)
MySQL slow query logs show long execution times for:
- CALL sp_batch_update_duplicate_step_item(...)

Resolution

Jama tracked this as defect SOS-DEF-9061, and it is fixed in Jama Connect® 9.36.0 (cloud), and will likely be included in the self-hosted version 9.4x.

Cloud

The issue should now be resolved for cloud customers.

Self-hosted

If the issue is present in a self-hosted environment, please submit a support request for temporary mitigation.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to