Error in custom process as seen the process instance message details:
File Load Error: org.apache.commons.jelly.JellyTagException: null:45:80: <core:invoke> method prepareStatement threw exception: PooledConnection has already been closed.
Release : 16.0.1
The error means the connection was closed too soon in the logic.
Therefore the connection close must be placed after the logic where the input file has been read completely.
Support does not correct and implement processes involving GEL scripts, therefore the correction will need to be made and validated from the team that implemented the process.
If it needs a maintenance contract, the Broadcom account manager will need to be engaged.