-
Notifications
You must be signed in to change notification settings - Fork 33
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
docs.javadsl.MqttFlowTest: bidirectional connection may leak actors #468
Labels
Comments
Closed
Merged
raboof
changed the title
docs.javadsl.MqttFlowTest: leaks actors
docs.javadsl.MqttFlowTest: bidirectional connection may leak actors
Jul 7, 2024
raboof
added a commit
to raboof/incubator-pekko-connectors
that referenced
this issue
Jul 7, 2024
While looking into apache#468, I noticed the two failing tests were sharing the same session id, which reminded of apache#456. While in this case the two tests aren't sharing the same session, and I haven't investigated the details of this codebase further, I'm curious to see if the problem remains when we use unique session ids.
raboof
added a commit
to raboof/incubator-pekko-connectors
that referenced
this issue
Jul 7, 2024
While looking into apache#468, I noticed the two failing tests were sharing the same session id, which reminded of apache#456. While in this case the two tests aren't sharing the same session, and I haven't investigated the details of this codebase further, I'm curious to see if the problem remains when we use unique session ids.
raboof
added a commit
that referenced
this issue
Jul 7, 2024
While looking into #468, I noticed the two failing tests were sharing the same session id, which reminded of #456. While in this case the two tests aren't sharing the same session, and I haven't investigated the details of this codebase further, I'm curious to see if the problem remains when we use unique session ids.
raboof
added a commit
to raboof/incubator-pekko-connectors
that referenced
this issue
Jul 8, 2024
(let's close this for now in case #736 was it, and re-open when it turns out it wasn't) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems to be specifically
establishClientBidirectionalConnectionAndSubscribeToATopic
andestablishServerBidirectionalConnectionAndSubscribeToATopic
The text was updated successfully, but these errors were encountered: