No worker running when facing `Terminating in response to exception`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 630
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
I get Terminating in response to exception when jedis throw an Unable to validate object exception.
I use jstack and there is no worker thread running, how can i resolve this? Thanks!
I run jesque on multiple machines(about eight instances).
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 with the reported Terminating in response to exception message, the Jedis Unable to validate object exception, and the jstack observation that no worker thread is running. Reproduce the behavior across the roughly eight Jesque instances and determine the worker lifecycle state and resolution; completion should explain why the worker stops and how to recover it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100