ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Time Slicing job failures - troubleshooting / known causes

book

Article ID: 130257

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Tips to aid in troubleshooting time slicing job failures

Resolution

Check bg-ca.logs for blobcrack errors

  • See KB Accessing the app-ca.log or other Clarity Logs for steps on how to access the bg-ca.logs (and other logs for both On Premise and SaaS customers)
  • Debugging configuration: If there are no relevant errors related to time slicing found in the logs, for each server's logging configuration, confirm the following components are set accordingly:

Priority

Name (Component) 

Appender

WARN

com.niku STDOUT
FATAL org.jgroups    STDOUT
ERROR org.logicalcobwebs.proxool STDOUT
ERROR com.niku.blobcrack STDOUT
ERROR com.niku.njs  STDOUT

See KB Setting Logging Levels in Clarity for more details on verifying/setting up the above debugging. 

Review Related KBs

Deadlocks

General Deadlock issues

MS SQL Server Database Specific

Defects Fixed in 15.9.1

Defects Fixed in 15.9.2

Defects Fixed in 15.9.3

Other Job Failures

Time Slicing job Stuck / Hanging / Slow

Additional troubleshooting help

If Broadcom support assistance is needed, the below information can aid in troubleshooting:

  1. Do other jobs appear to be running okay?  
  2. If On Premise, provide a copy of the bg-ca.logs and bg-system.logs for the time frame the issue occurred. 
  3. Is the Administration > Time Slices page up-to-date or behind? (It should all be caught up by the frequency of the scheduled Time Slicing job.
  4. If the job is supposed to run every minute, then the "Last Run Date" should be reflecting the closely to that frequency.)
  5. Does the job fail consistently or intermittently? 

Additional Information

See also: