You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 14, 2025. It is now read-only.
somehow the batch job in the composed task got the error:
org.springframework.dao.DataAccessResourceFailureException: PreparedStatementCallback; SQL [SELECT TASK_EXECUTION_ID, START_TIME, END_TIME, TASK_NAME, EXIT_CODE, EXIT_MESSAGE, ERROR_MESSAGE, LAST_UPDATED, EXTERNAL_EXECUTION_ID, PARENT_EXECUTION_ID from BOOT3_TASK_EXECUTION where TASK_EXECUTION_ID = ?]; This connection has been closed.; nested exception is org.postgresql.util.PSQLException: This connection has been closed.
after this error the composed task got restarted from 0
Interesting thing is that when we have the batch job without parallel flows and throws the exception - the whole composed task stops, which is good, but in this case the batch job has the parallel flows instead of steps and then after this exception we got the troubles, is it expected? Cause I can't find the docs about it, is there anything I can configure?