PPMBroker errors with status code = 401 on processes
search cancel

PPMBroker errors with status code = 401 on processes

book

Article ID: 372091

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

On a large system with PPMBroker configured and lots of records in cmn_broker_services, we see lots for errors in bg-ca on process pipelines, and process delays are observed

 

STEPS TO REPRODUCE:

  1. On a large customer using heavily MUX and ppmbroker configured on the system
  2. Connect with an admin user
  3. Run processes on a custom MUX object or Status Report object, containing gel scripts and UI actions and running for longer time typically
  4. Once you start the processes, log out

Expected Results: The processes to run smoothly and broker messages to complete

Actual Results: ERROR 2024-07-11 20:33:39,150 [Action Execution Pipeline 0 (tenant=clarity)] client.errorhandler (clarity:process_admin:49492792__0BCF655D-D2B0-4A28-918C-7513FB1A2792:invokeService.ppm-push) () Service invocation for service UUID 7438EE12-BA57-45F8-9F62-0BF3C23F4415 failed with status code = 401
ERROR 2024-07-11 20:33:39,151 [Action Execution Pipeline 0 (tenant=clarity)] client.errorhandler (clarity:process_admin:49492792__0BCF655D-D2B0-4A28-918C-7513FB1A2792:invokeService.ppm-push) () Service invocation parameters={BROADCAST=BROADCAST_SUBSCRIPTION, userName=admin, type=ppm-instance-update, message={"objectCode":"cop_prj_statusrpt","pk":5579188}, uuid=7438EE12-BA57-45F8-9F62-0BF3C23F4415}

Environment

Clarity 16.2.x with Broker configured

Resolution

This is DE116112, fixed in 16.2.3