Since 16.2.3 upgrade observing errors "Session in use count already reached to 0" in the bg-ca.log

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Since 16.2.3 upgrade observing errors "Session in use count already reached to 0" in the bg-ca.log.

Steps to Reproduce: 

1. Create simple process with the GEL script
2. Run the process to completion
3. Check bg-ca.log
4. Observe error "Session in use count already reached to 0"

Expected Results: It should not throw the error in the logs

Actual Results: It is flooding the bg-ca.log in the environment which is running many GEL processes

Cause

DE154678

Resolution

DE154678 is fixed in 16.3.1.

Additional Information

Larger extract of the message:

FATAL 2024-10-31 11:22:41,860 [Custom script execution pool-5-thread-1] union.cache (clarity:user:session:none) () Session in use count already reached to 0 at 
    com.niku.union.utility.caching.CacheController.setSessionInUse(CacheController.java:963)