NullPointerException for node auto shut down service during data import

XMLWordPrintable

    • 8.1
    • Severity 3 - Minor

      Issue Summary

      Data import remove all values from the database that cause that NodeAutoShutdownIfOfflineService can not get the current node state what causes NullPointerException.

      Steps to Reproduce

      1. Start 1 DC Jira node,
      2. Start restoring instance from the backup,
      3. In the log files, you can find a stack trace for NullPointerException for NodeAutoShutdownIfOfflineService.

      Expected Results

      There is no any NullPointerException for NodeAutoShutdownIfOfflineService

      Actual Results

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

      heartbeat-scheduler-0 ERROR[c.a.j.cluster.lock.StartableClusterNodeHeartbeatService] Unhandled exception occurred in heartbeat service java.lang.NullPointerException 
      at com.atlassian.jira.cluster.service.NodeAutoShutdownIfOfflineService.checkCurrentNodeState(NodeAutoShutdownIfOfflineService.java:61) 
      at com.atlassian.jira.cluster.lock.ClusterHeartbeatJob.run(ClusterHeartbeatJob.java:36) 
      at com.atlassian.jira.cluster.lock.StartableClusterNodeHeartbeatService.lambda$createHeartbeatJobWrapper$0(StartableClusterNodeHeartbeatService.java:114) 
      at com.atlassian.jira.util.thread.JiraThreadLocalUtils.lambda$wrap$1(JiraThreadLocalUtils.java:156) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) 
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
      at java.lang.Thread.run(Thread.java:748)
      

      Workaround

      There is no workaround.
      This issue should not harm your node functionality when the data import finishes.

            Assignee:
            Maria Marzec
            Reporter:
            Stasiu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: