Open JamesXNelson opened 6 years ago
Closing, this points to the the server's onError being correctly called after all, it just failed to handle it correctly.
Reopening - it wouldn't have helped this case, but the default impl of onError should spit out at least a stack trace, and a note to provide your own impl of the method for more appropriate logging (such as killing the connection).
Including stacktrace for posterity.