You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
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
The text was updated successfully, but these errors were encountered:
[apache#26203] fix(JmsIO): use a unused port for tests in JmsIO apache#26203Fixesapache#27312, apache#26203
Co-Authored-By: Amrane Ait Zeouay <122456352+amranezeRenault@users.noreply.github.com>
Amraneze
added a commit
to Amraneze/beam
that referenced
this issue
Jun 30, 2023
[apache#26203] fix(JmsIO): use a unused port for tests in JmsIO apache#26203Fixesapache#27312, apache#26203
Co-Authored-By: Amrane Ait Zeouay <122456352+amranezeRenault@users.noreply.github.com>
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
The text was updated successfully, but these errors were encountered: