Akka.IO: TcpConnection does not propagate closure events reliably
#7634
Labels
Milestone
Comments
Aaronontheweb
added
potential bug
akka-io
confirmed bug
and removed
potential bug
labels
Aaronontheweb
added a commit
to Aaronontheweb/akka.net
that referenced
this issue
May 12, 2025
6 tasks
Aaronontheweb
added a commit
that referenced
this issue
May 12, 2025
* Akka.IO: added `TcpListenerStatistics` and subscription methods This enables the `Akka.IO.TcpListener` to periodically publish connectivity statistics to subscribers on `10s` intervals - designed to help create telemetry for servers built on top of Akka.IO. close #7631 * added documentation * remove duplicate `ConnectionTerminated` * tried to add closure check but ran into #7634
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Version Information
Version of Akka.NET? v1.5.41
Which Akka.NET Modules? Akka.IO
Describe the bug
Yet another Akka.IO bug - while working on #7633 I tried to tests to verify that we can track connection closures, but there's a small problem: the
TcpConnectionactor doesn't reliably transmit this information.Expected behavior
If the remote socket gets closed, the local socket should close and report back to its handler immediately.
Actual behavior
Wildly different stuff depending on how the socket was closed. Sometimes an event, usually not.
Additional context
This code is wildly over-engineered and is in drastic need of cleanup.
The text was updated successfully, but these errors were encountered: