CarlosJuncher03 opened a new issue, #8568: URL: https://github.com/apache/hop/issues/8568
### Apache Hop version? CachingDatabaseExecutionInfoLocation keeps using a closed database connection after stopping a workflow ### Java version? 21 ### Operating system Linux ### What happened? When using Caching Database Execution Information Location, stopping a running workflow and then running it again causes Apache Hop to continuously print database errors. The execution information cache appears to keep trying to persist data using a JDBC connection that has already been closed. Steps to reproduce Configure a Workflow Run Configuration using Caching Database Execution Information Location. Start a workflow. Stop the workflow while it is running. Run the workflow again. Hop starts continuously logging errors related to the execution information database. Observed error Caused by: org.apache.hop.core.exception.HopDatabaseException: An error occurred executing SQL: SELECT 1 FROM "HOP_EXECUTIONS"."HOP_EXECUTIONS" WHERE "id" = ? This connection has been closed. at org.apache.hop.execution.database.CachingDatabaseExecutionInfoLocation.rowExists(...) at org.apache.hop.execution.database.CachingDatabaseExecutionInfoLocation.upsertCacheEntry(...) at org.apache.hop.execution.database.CachingDatabaseExecutionInfoLocation.persistCacheEntry(...) at org.apache.hop.execution.caching.BaseCachingExecutionInfoLocation.manageCache(...) at java.base/java.util.TimerThread.mainLoop(...) at java.base/java.util.TimerThread.run(...) ### Issue Priority Priority: 3 ### Issue Component Component: Infrastructure -- 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]
