Should not schedule to stop Clarity and to start jobs at the same time.

book

Article ID: 52934

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Description:

Scheduling to start Clarity jobs is common practice. Users also can schedule to start/stop Clarity via wrapper with auto setting. If the Clarity job start time and the Clarity shutdown time are scheduled at the same time, fatal errors could be thrown at the time of Clarity shutdown.

The typical error messages with Clarity shutdown time of 00:00 are:

  1. FATAL 2012-09-29 00:00:03,718 [Dispatch Thread-1291: [email protected]] union.persistence (none:none:none) Failed to determine analytic function support java.lang.RuntimeException: Unexpected invocation exception: [CA Clarity][Oracle JDBCDriver]Object has been closed.

  2. FATAL 2012-09-29 00:00:03,718 [Dispatch Thread-1291: [email protected]] union.persistence (none:none:none) Failed to retrieve database version java.lang.RuntimeException: Unexpected invocation exception: [CA Clarity][Oracle JDBC Driver]Object has been closed.

Although they are recorded as Fatal, they can be ignored and Clarity can be restarted without any problem.

The wrapper is often scheduled to stop Clarity daily or weekly at usually at xx:00. On the other hand the Clarity jobs are often scheduled recursively every hour or minute. The job start time is likely scheduled at the same time of the wrapper's Clarity shutdown time unintentionally. The above error messages are example while a Clarity job is scheduled to start hourly with 00,10,20,30,40,50 min.

Solution:

Avoid scheduling wrapper's Clarity shutdown time and Clarity job start time at the same time.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component: