ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Process Error : "script has leaked 1 JDBC Connections"


Article ID: 237162


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Custom process is failing with process error message detail:
"script has leaked 1 JDBC Connections"


Starting in 16.0.01 and 16.0.1, the GEL scripts will need to be reviewed for JDBC connection leaks as the process will be evaluated at runtime for leaks.
This is to prevent BG connection pool exhaustion.

If a connection is made like this:
    <gel:setDataSource dbId="niku" var="clarityDB"/>
    <core:invoke method="getConnection" on="${clarityDB}" var="ppmDbConn"/>

the connection will need to be closed with the following example:"
<core:invoke method="close" on="${ppmDbConn}"/>

Additional Information

Please refer to the following article which addresses preventing connection leaks:
Database connections in GEL scripts best practices