Clarity PPMBroker INSERT failing in a clustered broker environment on service_type column
search cancel

Clarity PPMBroker INSERT failing in a clustered broker environment on service_type column

book

Article ID: 377047

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

When ppmbroker is set up in a clustered environment, the call is not able to determine the service type correctly and INSERT fails on 16.2.3

STEPS TO REPRODUCE:

  1. Set up a clustered broker environment with 2+ ppmbroker services on Clarity 16.2.3

Expected Results: Broker requests to go through accordingly

Actual Results: CMN_BROKER_SERVICES inserts fail with error ERROR: null value violates not-null constraint on service_type column

Full Error:

ERROR 2024-09-11 10:44:49,939 [clarity.xxxxxx:PPMThreadPoolWorker-3624:ppm-push] broker.service (clarity.xxxx:xxxx:56876620__9FFCEB80-B063-47BD-9421-B66651DF3FF7:none) () 
com.niku.union.persistence.PersistenceException: 
SQL error code: 0
Error message: ERROR: null value in column "service_type" of relation "cmn_broker_services" violates not-null constraint
  Detail: Failing row contains (22987268, DBF30CD9-D870-44B2-B852-9F8A632130DA-D0D27172-7057-459F-B95C-0A6..., ppm-push, INITIATED, 2024-09-11 10:44:49.937, 5002001, 2024-09-11 10:44:49.937, 5002001, null).
Executed:
 INSERT INTO CMN_BROKER_SERVICES (ID, CODE, UUID, STATUS, CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY, SERVICE_TYPE)
          VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?)

Environment

Clarity 16.2.3

Cause

DE153775

Resolution

This is DE153775, fixed in 16.3.0

Workaround: Use a non-clustered ppmbroker environment

Powered by Wolken Software