mattcasters opened a new issue, #9107: URL: https://github.com/apache/hop/issues/9107
### Apache Hop version? SNAPSHOT-20261026 ### Java version? 21 ### Operating system Linux ### What happened? `CachingDatabaseExecutionInfoLocation` keeps one JDBC session for the execution-information cache. After a statement fails, PostgreSQL aborts that transaction. Later writes on the same session then fail with `25P02` (`current transaction is aborted`) or with `42P01` / `3F000` (`relation "hop_executions" does not exist` or an invalid schema), even when `public.hop_executions` is still there. The session search path or a prepared statement left from a dropped table is stale. A new connection succeeds. The location already retries a closed connection (`08003`). It does not recover an aborted or stale session, so execution logging stays broken until Hop is restarted. Commit is not a recovery: PostgreSQL rejects `COMMIT` once a statement in the transaction has failed. Roll the failed session back, drop it, and retry the write once on a new connection. ### Issue Priority Priority: 2 ### Issue Component Component: Database 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]
