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
Describe the bug
When conductor loses connection to postgres for a period of time and the newSingleThreadScheduledExecutor that executes processAllUnacks throws an exception (due to loss of connection or any other reason), no more task are scheduled.
Describe the bug
When conductor loses connection to postgres for a period of time and the
newSingleThreadScheduledExecutor
that executesprocessAllUnacks
throws an exception (due to loss of connection or any other reason), no more task are scheduled.Details
Conductor version: All
Persistence implementation:Postgres
Queue implementation: Postgres
Lock: Redis
Workflow definition:
Task definition:
Event handler definition:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The thread should continue attempts to execute
processAllUnacks
as postgres connection will eventually recover.Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
https://stackoverflow.com/questions/6894595/scheduledexecutorservice-exception-handling
The text was updated successfully, but these errors were encountered: