Configuring OpenSearch on an uninitialised Jira, blocks Jira from starting up

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 11.3.1
    • Affects Version/s: 11.0.0, 11.1.0, 11.0.1, 11.1.1, 11.2.0, 11.2.1, 11.3.0
    • Component/s: OpenSearch
    • None
    • 11
    • 1
    • Severity 3 - Minor

      Issue Summary

      Jira Data Center fails to start when a newly initialized instance is configured to use OpenSearch as the search backend before completing initial setup.

      Steps to Reproduce

      1. Deploy a new (uninitialized) Jira Data Center instance.
      2. Before completing the initial setup wizard, configure the instance to use OpenSearch as the search engine (e.g., by setting search.platform=opensearch in the jira-config.properties file).
      3. Start Jira.

      Expected Results

      Jira starts successfully, completes initialization, and is ready for use with OpenSearch as the search backend.

      Actual Results

      Jira fails to start correctly.

      The below exception is thrown in the atlassian-jira.log file:

      ERROR      [c.a.jira.ofbiz.ChainedSQLInterceptor] Unexpected exception in com.atlassian.jira.ofbiz.InstrumentedSQLInterceptor@631f188a
      java.lang.IllegalStateException: A jira-core bean has tried to access the database during context refresh. DB access should not happen in constructors. This error should be reported to Atlassian.
      	at com.atlassian.jira.instrumentation.Instrumentation.getInstance(Instrumentation.java:67)
      	at com.atlassian.jira.instrumentation.Instrumentation.putInstrument(Instrumentation.java:73)
      	at com.atlassian.jira.ofbiz.InstrumentedSQLInterceptor.onConnectionTaken(InstrumentedSQLInterceptor.java:31)
      ...
      

      Workaround

      Run through the setup process before configuring the search platform to OpenSearch.

            Assignee:
            Hendry Luk
            Reporter:
            Will Yasvoin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: