search cancel

Time Slicing Job Keeps Retrying After Failing


Article ID: 239107


Updated On:


Clarity PPM On Premise


On a Clarity Oracle databasem, the Time Slicing job is failing every 5 minutes and attempting restart each time. It will do this indefinitely.

The BG logs shows errors:

WARN  2022-04-08 10:43:51,525 [Dispatch Time Slicing: [email protected] (tenant=clarity)] persistence.PersistenceController (clarity:user:session:Time Slicing) Warning: Attempting to reuse a closed connection.
ERROR 2022-04-08 10:43:51,525 [Dispatch Time Slicing: [email protected] (tenant=clarity)] persistence.PersistenceController (clarity:user:session:Time Slicing) 
 at com.niku.union.persistence.PersistenceController.createLocalContext(
FATAL 2022-04-08 10:43:51,525 [Dispatch Time Slicing-prad : [email protected] (tenant=clarity)] union.persistence (clarity:user:session:Time Slicing) Failed to determine analytic function support
java.sql.SQLException: [CA Clarity][Oracle JDBC Driver]Object has been closed.


Release : 16.0.0

Component : Clarity Job Scheduler


The retry timeout can vary and 5 minutes is default.

The DBA team will need configure the connection pool setting.
This is to allow jobs such as the Time Slicing job to complete, which can take 4+ hours to complete.