Who or what restarted Clarity APP or BG
search cancel

Who or what restarted Clarity APP or BG


Article ID: 255322


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Clarity App or Bg was restarted and a message similar to this:

SYS   2022-11-13 05:02:02,486 [BG Shutdown] niku.njs (clarity:none:none:none) Thread Pool: java.util.concurrent.ThreadPoolExecutor@1965ff8c[Running, pool size = 10, active threads = 0, queued tasks = 0, completed tasks = 20242]

SYS   2022-11-13 05:02:02,476 [Thread-3] bpm.engine (none:none:none:none) Process Controller for engine bg-S3B9367 stopping...

SYS   2022-11-13 05:02:02,477 [Thread-772] njs.SchedulerImpl (none:none:none:none) PPM Job Scheduler stopping...

We are looking to understand who restarted the service? 


  • There is no way to determine if this was manual or an OS restart based on this error
  • You have to check OS event logs to see if there was a system restart during that time
  • Also this may have been done by someone directly or indirectly (via the command or via scripts)
  • Review the bg-system logs for any clues
    • If you have an OOM error then:
    • Check if you have set up heap dumps on OOM on BG in properties.xml (provide if needed) Check if any got generated in the indicated directory on those times