spring-projects / spring-projects/spring-session
Default pool size for the Redis RedisMessageListenerContainer.taskExecutor
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
The RedisMessageListenerContainer uses a SimpleAsyncTaskExecutor to dispatch the messages. This causes problems regarding thread creation and repletion, see issue https://github.com/spring-projects/spring-session/issues/483.
It makes sense to make spring-session inject a Pooled TaskExecutor into spring-data-redis. We use a pool size of 10.
Contributor guide
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 tracing how RedisMessageListenerContainer configures its taskExecutor and review the related spring-session issue 483 for the thread-creation problem. The change is done when spring-data-redis receives a pooled task executor with a pool size of 10 and message dispatch no longer relies on the SimpleAsyncTaskExecutor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100