Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.1.0
-
None
Description
Currently, as I see from Nio2Acceptor and Nio2Session code we call socket async read/write without specifying ant timeouts. This may mean that for some cases this read/write may stuck eternally.
Currently I see such dangling connections on my application.
It could be nice if we were ably to pass some fixed timeout for low-level socket operations.