conductor-oss / conductor-oss/conductor

[Bug] PostgresQueueDao processAllUnacks thread dies silently

Open
#326 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
Java
Stars
32.2k
Forks
1k
Avg merge
2d 3h
Merged PRs (30d)
37

Description

**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.

**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:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.