Processes failing / Process Engines in Stopped Status

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Processes were previously running successfully but have all started failing. Checking the Process Engine status in Clarity in Administration->Data Administration->Process Engines, all Process Engines are in a stopped status.

Reviewing the bg-ca.logs, the following error may also be found:
ERROR 2020-02-26 09:12:24,726 [Post Condition Transition Pipeline 1 (tenant=clarity)] bpm.engine (clarity:process_admin:.....) Error in pipeline
com.niku.bpm.BpmException: Cannot get DB Connection
 at com.niku.bpm.engine.persistence.BpmContext.getContext(BpmContext.java:137)
 at com.niku.bpm.engine.persistence.BpmContext.getContext(BpmContext.java:109)
 at com.niku.bpm.engine.persistence.BpmContext.getContext(BpmContext.java:97)
 at com.niku.bpm.engine.rules.Pipeline.run(Pipeline.java:279)
Caused by: java.sql.SQLException: Connection unavailable
 at com.niku.union.persistence.connection.ApacheContext.getConnection(ApacheContext.java:194)
 at com.niku.union.persistence.connection.ApacheContext.getConnection(ApacheContext.java:185)
 at com.niku.bpm.engine.persistence.BpmContext.getContext(BpmContext.java:132)
 ... 3 more

Environment

Release : All Supported Releases

Component : CA PPM SAAS BUSINESS PROCESS MANAGEMENT

Resolution

Restart all BG Services for the impacted environment

(SaaS customers, please contact Broadcom support for assistance)

Additional Information

See Searching for known Clarity Issues using Self Service