search cancel

Job with long name completes but throws multiple FATAL errors

book

Article ID: 254951

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

Running a job with a very long with a long Job Name makes the logs show a FATAL error, although the job completes successfully.

Steps to Reproduce:

  1. Go to Home > Reports and Jobs > Jobs > Available and click on any Job Type, like "Clean User Session".
  2. In the Job Name field, use a very long name, such as "This is a very long job name. It is crazy how long this name is, isn't it?"
  3. Submit the job for an immediate run.

Expected Results: The job completes. The bg-ca.log does not show any error for this job run.

Actual Results: The job completes. The bg-ca.log shows multiple FATAL errors, like:

FATAL 2022-11-24 03:15:08,959 [Dispatch This is a very long job name. It is crazy how long this name is, isn't it? : [email protected] (tenant=clarity)] union.persistence (clarity:admin:xxx:This is a very long job name. It is crazy how long this name is, isn''t it?) 
java.sql.SQLClientInfoException: Invalid or unsupported name for clientInfo.
 at oracle.jdbc.driver.PhysicalConnection.setClientInfo(PhysicalConnection.java:7563)
 [...]

Environment

Release : 16.0.3

Cause

DE67483

Resolution

This issue is under review.

Workaround:

Use a shorter job name.