Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: SolaceIO.Read: clients are not properly closed. #31965

Closed
1 of 17 tasks
bzablocki opened this issue Jul 24, 2024 · 1 comment
Closed
1 of 17 tasks

[Bug]: SolaceIO.Read: clients are not properly closed. #31965

bzablocki opened this issue Jul 24, 2024 · 1 comment
Assignees

Comments

@bzablocki
Copy link
Contributor

What happened?

When reading from Solace, especially with DirectRunner which by-design closes randomly UnboundedReaders, some of the connections were not properly closed.
A way to fix it is to explicitly close the FlowReceivers created from JcsmpSession objects, instead of closing only the JcsmpSession objects.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@bzablocki
Copy link
Contributor Author

.take-issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant