Starting the background service for job scheduling and process engine after a previous controlled shutdown may start and then stop and fail with an error shortly after whilst it is initializing with the FATAL level error message "java.sql.SQLException: We are already in the process of making 11 connections and the number of simultaneous builds has been throttled to 10" reported in the logs.
The behavior is very intermittent and may go without warning for a period of months before returning suddenly again. When the problem is occurring, process engine events may not be actioned and scheduled jobs or reports will not be run.
Steps to Recreate:
Logs consistently report bg service initialized and ready and the status command indicates the bg service is still running
Logs intermittently reported FATAL exception error and the service status may show it in a stopped state
Since the service is already stopped as part of scheduled maintenance, the need is to get the service started again. The following steps have succeeded in this for some environments:
This issue has been documented as CLRT-48675 and is fixed in Clarity version 12.0.6.
CLARITYKB, CLRT-48675, clarity8open, clarity12open