PoolManager for closures is not thread safe
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
A closure can be called from multiple threads. The PoolManager however is not thread safe, which is an issue.
Make PoolManager TLS?
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 locating the PoolManager implementation and the closure call path described in the issue. Inspect how pool state is shared when closures run on multiple threads, then reproduce the concurrent case before choosing a thread-safety approach. Done means concurrent closure calls no longer expose unsafe PoolManager behavior, with coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100