Issue Summary

The Assets health check endpoints ("/rest/insight/1.0/health/consistency/duplicates/attributevalues" and "/secure/admin/InsightPluginHealthCheck.jspa") are timing out on Jira 10.3.10 LTS for instances with a high volume of data (over 6 million attribute records), despite having zero duplicate attribute values. The same process completed successfully on Jira 10.3.8. This indicates a regression in the health check's underlying query logic in the newer version.

Steps to Reproduce

1. Upgrade a Jira Service Management Data Center instance to 10.3.10 LTS.
2. Ensure the Assets database has a large number of records (e.g., over 6 million in the "AO_8542F1_IFJ_OBJ_ATTR" table).
3. Attempt to access the hidden health check page as an admin: https://<Jira_base_URL>/secure/admin/InsightPluginHealthCheck.jspa
4. Alternatively, execute a GET request to the REST endpoint: GET /rest/insight/1.0/health/consistency/duplicates/attributevalues

Expected Results

The health check completes within a reasonable time (e.g., 5-8 seconds as observed in 10.3.8) and returns a JSON response indicating the status, or the UI page loads and confirms "No duplicate attribute values found."

Actual Results

The request times out after the configured server limit (e.g., 60 seconds on the public URL, 300 seconds on the internal Tomcat port).
The exception below is thrown in the atlassian-jira.log file, specifically a StuckThreadDetectionValve warning, which points to the underlying long-running query:

22-Sep-2025 00:12:27.023 WARNUNG [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-10.0.1.2-8081-exec-73 url: /rest/insight/1.0/health/consistency/duplicates/attributevalues; user: honicon-service] (id=[14612]) has been active for [123.318] milliseconds (since [22.09.25 00:10]) to serve the same request for [https://jira.honicon.com/rest/insight/1.0/health/consistency/duplicates/attributevalues] 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 com.riadalabs.jira.plugins.insight.services.core.dal.impl.ObjectDalImpl.findDuplicateObjectAttributeValueIds(ObjectDalImpl.java:524)

at com.riadalabs.jira.plugins.insight.services.core.dal.impl.ObjectDalImpl.removeDuplicates(ObjectDalImpl.java:464)

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: