-
Notifications
You must be signed in to change notification settings - Fork 97
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
Some remote peers remain connected even after calling close
on TcpDuplexConnection
#226
Labels
1.0
Pullrequests & issues related to the Typescript rewrite and 1.0 release
Comments
viglucci
added
the
1.0
Pullrequests & issues related to the Typescript rewrite and 1.0 release
label
May 8, 2022
@viglucci I believe Environment
web browser console log output and server side log looks like below when call
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Remote peer is disconnected when calling
this.socket.end()
inTcpDuplexConnection.close()
.Actual Behavior
Some remote peers (clients) do not respect the
end()
call and are able to still transmit data to the server, which results in NPEs and other undefined behavior.This behavior was experienced from a
.Net
TCP Client in Unity RSocket.Steps to Reproduce
Not available.
Possible Solution
TcpDuplexConnection
may need to additionally, or in lieu ofend()
, calldestroy()
onthis.socket
whenclose
is called.Your Environment
netty
, ...): n/ajavar -version
) or Node version (node --version
)): node: v16.13.1uname -a
): n/aThe text was updated successfully, but these errors were encountered: