[Bug]: JmsIO create connection based on the number of threads
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 204
Description
### What happened?
JmsIO doesn't support for now connection pooling and retrying the publishing messages in case of a failure. It would be nice to have a connection pool so that the user can decide how many connections can be used for each worker.
### Issue Priority
Priority: 2
### Issue Components
- [ ] Component: Python SDK
- [X] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [X] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
Contributor guide
Research direction
Start by locating JmsIO in the Java SDK's IO connector code and inspect how connections are created per worker and thread. Define the expected connection-pool sizing and publishing retry behavior, then identify tests that can demonstrate user-selected connections and recovery after a publish failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100