Insight custom field value couldn't be saved due to StackOverflowError

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      After upgrading Insight plugin to 8.7.10, editing Insight custom field value may fail due to StackOverflowError.

      Steps to Reproduce

      This is not affecting every customer and there are yet to be confirmed steps to reproduce this, but a circular dependency is possible from the code level which has been identified.

      1. Upgrade Insight plugin to 8.7.10.
      2. Edit a Jira issue and edit an existing Insight custom field value, or edit an existing Insight custom field value inline.

      Expected Results

      The value of the Insight custom field is saved without error

      Actual Results

      The screen may be unresponsive for a while like it's taking some time to save the value. After that, the StackOverflowError is shown on the screen and the new value is not saved. You may still see a spinning wheel at the Insight custom field you edited, refresh the page and the spinning wheel and error will be gone but the value is still not saved.

      The below exception is thrown in the atlassian-jira.log file. We can see deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira) multiple times in the end of the stack trace.

      2021-07-11 13:42:33,375+0000 http-nio-8080-exec-2 ERROR admin 720x5187x1 1ny19sw 10.29.10.100 /secure/AjaxIssueAction.jspa [c.a.j.c.issueviewer.action.AjaxIssueAction] Exception occurred editing issue: java.lang.StackOverflowError
java.lang.StackOverflowError
...
	at com.riadalabs.jira.plugins.insight.services.core.dal.dao.impl.InsightActiveObject.get(InsightActiveObject.java:66)
	at com.riadalabs.jira.plugins.insight.services.core.dal.dao.impl.ObjectJiraIssueDaoImpl.loadObjectJiraIssueAO(ObjectJiraIssueDaoImpl.java:51)
	at com.riadalabs.jira.plugins.insight.services.core.dal.impl.ObjectTicketConnectionDalImpl.loadObjectTicketConnection(ObjectTicketConnectionDalImpl.java:48)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:77)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
	at io.riada.insight.external.services.ObjectTicketConnectionServiceInJira.deleteObjectTicketConnection(ObjectTicketConnectionServiceInJira.java:88)
...

      Workaround

      If this happens after the upgrade of the Insight plugin, revert to the previous version

            Assignee:
            François Dénommée (Inactive)
            Reporter:
            Michelle Chin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: