Worker existing on uncaught exception after 10 minutes of no connection
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 630
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
After 10 minutes (BTW - non configurable) of no connection to Redis server
https://github.com/gresrun/jesque/blob/c6653eda6d3c3b7ef03ad5c7612dce987170e62e/src/main/java/net/greghaines/jesque/worker/WorkerImpl.java#L66
The worker process is terminated with uncaught exception
https://github.com/gresrun/jesque/blob/c6653eda6d3c3b7ef03ad5c7612dce987170e62e/src/main/java/net/greghaines/jesque/worker/WorkerImpl.java#L227
when trying to reach Redis in the finally block after poll() method ended with shutdown request.
Jedis is not connected and throwing uncaught error. Not sure that this is the expected behavior, however I guess the outcome is the same :) ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading src/main/java/net/greghaines/jesque/worker/WorkerImpl.java at the references around lines 66 and 227. Reproduce a Redis connection loss followed by a shutdown request, then verify that the worker no longer terminates with an uncaught exception while handling the shutdown path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100