mattcasters opened a new issue, #6714: URL: https://github.com/apache/hop/issues/6714
### Apache Hop version? 2.18.0-SNAPSHOT ### Java version? OpenJDK 21 ### Operating system Linux ### What happened? Reproduction steps: * There is a pipeline that calls another pipeline by using a pipeline executor * The called pipeline starts with the make transactional flag set. It starts by executing a table input * Next, after that first step, the nework connection goes down for a while and during that the called pipeline tries to perform a dblookup. * Because the connection is not available the dblookup raises an exception and the called pipeline starts by trying to rolback something in progress * The called pipeline exits it processing but the calling pipeline got stuck and is unable to terminate normally. * This inability to close the calling pipeline normally too is causing a lot of problem Root cause analyses: * In both LocalPipelineEngine and LocalWorkflowEngine we add an execution finished listener which tries to commit or rollback a database connection when running in "Transactional" mode. The exceptions that are generated by these operations when the database in question is not available are not properly handled. * This causes the exception to propagate upward * This causes the execution finished listeners loop to stop. * The pipeline or workflow in question never finishes when run in Hop Run. * In the Hop GUI, this exeception is caught and the pipeline terminated. Solution: * Properly handle the exception in the ExecutionFinishedListener of both LocalWorkflowEngine and LocalPipelineEngine. ### Issue Priority Priority: 0 ### Issue Component Component: Pipelines -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
