Stack trace is not returned when there’s an exception raised in c.a.j.index.ha.DefaultReplicatedIndexManager

XMLWordPrintable

    • 11.03
    • 1
    • Severity 3 - Minor
    • 2

      Issue Summary

      Stack trace is not returned when there’s an exception raised in c.a.j.index.ha.DefaultReplicatedIndexManager.
      This makes it difficult to determine what the root cause of the issue is which can block troubleshooting efforts.

      Steps to Reproduce

      The issue may appear in some instances of Jira Data Center 11.3.2 when index replication fails for an issue.
      There are no specific steps to reproduce this at the moment.

      Expected Results

      There’s an associated stack trace after the error. Here are some examples found from previous versions:

      2014-04-24 11:50:52,516 http-bio-1523-exec-8 ERROR localadmin 710x731x1 1a3wbvp 172.22.2.218 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [jira.index.ha.DefaultReplicatedIndexManager] Caught an exception trying to replicate reindexed issues.  The replicated index may or may not be correct
java.lang.NullPointerException
	at com.atlassian.jira.index.ha.DefaultReplicatedIndexManager$1.consume(DefaultReplicatedIndexManager.java:63)
	at com.atlassian.jira.index.ha.DefaultReplicatedIndexManager$1.consume(DefaultReplicatedIndexManager.java:59)
	at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:44)
	at com.atlassian.greenhopper.upgrade.IssueIdsIssueIterable.foreach(IssueIdsIssueIterable.java:32)
	at com.atlassian.jira.index.ha.DefaultReplicatedIndexManager.reindexIssues(DefaultReplicatedIndexManager.java:58)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:504)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:461)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:454)
...
2016-09-29 20:05:05,900 NodeReindexServiceThread:thread-1 ERROR [jira.index.ha.DefaultReplicatedIndexManager] Caught an exception trying to replicate deindexed shared entity. The replicated index may or may not be correct
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ReplicatedIndexOperation][indexTime,2016-09-29 20:05:05.809][filename,][entityType,SEARCH_REQUEST][affectedIndex,SHAREDENTITY][affectedIds,xxxx][id,null][operation,DELETE][nodeId,node5] (SQL Exception while executing the following:INSERT INTO replicatedindexoperation (ID, INDEX_TIME, NODE_ID, AFFECTED_INDEX, ENTITY_TYPE, AFFECTED_IDS, OPERATION, FILENAME) VALUES (?, ?, ?, ?, ?, ?, ?, ?) (ORA-01400: cannot insert NULL into ("<oracle_schema>"."REPLICATEDINDEXOPERATION"."ID")
))

      Actual Results

      The error is returned but provides no stack trace. Here are some examples found in 11.3.2:

      2026-04-29 15:21:05,624-0400 pool-1398-thread-1 ERROR      [c.a.j.index.ha.DefaultReplicatedIndexManager] Caught an exception trying to replicate reindexed ISSUE. The replicated index may or may not be correct
...
2026-05-05 14:21:37,932-0400 JiraTaskExecutionThread-450 ERROR abc     [c.a.j.index.ha.DefaultReplicatedIndexManager] Caught an exception trying to replicate reindexed ISSUE. The replicated index may or may not be correct

      Workaround

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

              Assignee:
              Sławomir Zaraziński
              Reporter:
              Adrian Castillo
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: