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}"/>
Please refer to the following article which addresses preventing connection leaks:
https://knowledge.broadcom.com/external/article?articleId=219510
Database connections in GEL scripts best practices