Clarity PPM: Connection leak issue in itd Advanced Resource Planning
Article ID: 186498
Clarity PPM SaaSClarity PPM On Premise
Advanced Resource Planning is a tool developed by partner ITD, the tool provides a feature allowing the configuration of customer defined actions which can be started from a context menu. When using customer defined process actions (ex. actions which start a custom Clarity PPM system process) a database connection is created, but not closed. The database connection will remain active. If the Oracle database has a max size on the connection pool, in time, the pool can be maxed out which would results in no available db connections.
STEPS TO REPRODUCE:-
An active Clarity system process (not an instance process). The process can be empty, no actions are required. An Advanced Resource Planning action (itd AE Actions List instance) configured to start the Clarity process. Example:
Note the number of active connections by using clarity_host/niku/apache?alias=clarity&level=more&pool=more
Go to Advanced Resource Planning, and start the Test process from there, by using the context menu item (ex. Test process). Do this a couple of times.
Check again the number of active connections. It will increase with each process started and remain high because the connections created during the process start are not being closed.
Expected Results: The number of active connection should be closed
Actual Results: Check again the number of active connections. It will increase with each process started and remain high because the connections created during the process start are not being closed.
This issue is being investigated and tracked via Clarity PPM Defect DE53944 and AE-3262 from ITDESIGN. Fix expected to be delivered in patch 3 of Clarity PPM release 15.7.1, and patch 1 of release 15.8- The fix is applicable to SAAS customers only.
Release : 15.7.1 and 15.8
Component : CA PPM INTEGRATIONS
ITD Advanced Resource Planning versions 7.7 and 8.0.
All the available JDBC connection is exhausted and the error in log is Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none available[size:1000; busy:1000; idle:0; lastwait:30000].
Interim resolution is to release connections. i.e., Killing the inactive connections from the database side and restarting Clarity PPM services.
Note: Restarting services is not a sustainable solution because the JDBC connections can continue to grow post restart as described above.