Processes stuck after upgrading to 16.2.3

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

1. Processes are getting stuck randomly or progress very slowly, slower than before upgrade. Following messages are visible in bg-ca.log:
   
   

   ERROR 2024-09-11 09:18:57,295 [Event Handler pool-3-thread-4] bpm.eventmgr (clarity:unknown:session:none) () An error occurred while processing event Event{_messageId='5672721', _objectTypeCode='stepaction', _objectId=5354662, _eventCode='BPM_SAE_DONE', _userId=8, _impersonatedBy=-1, _timestamp=2024-09-11 09:18:56.682, _autoStartProcessed=false, _deleteEventProcessed=true, _pushingEngineProcessed=false} java.lang.NullPointerException: Cannot invoke "com.niku.union.security.SecurityIdentifier.getSessionId()" because "secId" is null

   
   
   

   ERROR 2025-01-06 14:14:49,415 [Custom script execution pool-23-thread-3] union.gel (clarity:XXX:XXX__XXX-XXX-XX-XX-XXX:none) () GEL Script not using the correct connection pool! - ApplicationName: null
   FATAL 2025-01-06 14:14:51,675 [Post Condition Transition Pipeline 0 (tenant=clarity)] union.cache (clarity:process_admin:XXXX__XXXX-XXXX-XXX-XXX-XXX:none) () Session in use count already reached to 0 at 
   	com.niku.union.utility.caching.CacheController.setSessionInUse(CacheController.java:963)
   	com.niku.bpm.services.ProcessEngine.processComplete(ProcessEngine.java:470)
   	com.niku.bpm.engine.ProcessLoader.setProcessInstanceAsDone(ProcessLoader.java:585)
   	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.transitionStep(PostConditionTransitionPipeline.java:361)
   	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.processWaitingForTransitionSteps(PostConditionTransitionPipeline.java:297)
   	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.execute(PostConditionTransitionPipeline.java:103)
   	com.niku.bpm.engine.rules.Pipeline.run(Pipeline.java:279)

   
   
   
2. Processes that typically finish in less than a minute can all of a sudden take more time to complete.

Environment

Clarity 16.2.3

Cause

DE154010

Resolution

DE154010 Fixed in 

• Clarity 16.2.3 Patch 1 (16.2.3.1) 
• Clarity 16.3.0 Patch 1 (16.3.0.1)

 

• The process stuck issue is fixed via DE154010, however the error stack below will persist post the upgrade to the aforementioned releases. This error is benign and can be disregarded. A fix is planned to suppress this error in subsequent releases.

  ERROR 2025-01-06 14:14:49,415 [Custom script execution pool-23-thread-3] union.gel (clarity:XXX:XXX__XXX-XXX-XX-XX-XXX:none) () GEL Script not using the correct connection pool! - ApplicationName: null
  FATAL 2025-01-06 14:14:51,675 [Post Condition Transition Pipeline 0 (tenant=clarity)] union.cache (clarity:process_admin:XXXX__XXXX-XXXX-XXX-XXX-XXX:none) () Session in use count already reached to 0 at 
  	com.niku.union.utility.caching.CacheController.setSessionInUse(CacheController.java:963)
  	com.niku.bpm.services.ProcessEngine.processComplete(ProcessEngine.java:470)
  	com.niku.bpm.engine.ProcessLoader.setProcessInstanceAsDone(ProcessLoader.java:585)
  	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.transitionStep(PostConditionTransitionPipeline.java:361)
  	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.processWaitingForTransitionSteps(PostConditionTransitionPipeline.java:297)
  	com.niku.bpm.engine.rules.PostConditionTransitionPipeline.execute(PostConditionTransitionPipeline.java:103)
  	com.niku.bpm.engine.rules.Pipeline.run(Pipeline.java:279)