You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both server and client handlers simply log all caught exceptions. In case something goes wrong in the pipeline, processing might be stuck. E.g. when a server responds unexpectedly, Netty throws io.netty.handler.codec.EncoderException making the connection effectively useless. I'm not sure what is the best approach handling exceptions for the server, but at least for the client we probably need to clean up (close connection?) or propagate exception as the request result.
The text was updated successfully, but these errors were encountered:
Both server and client handlers simply log all caught exceptions. In case something goes wrong in the pipeline, processing might be stuck. E.g. when a server responds unexpectedly, Netty throws
io.netty.handler.codec.EncoderException
making the connection effectively useless. I'm not sure what is the best approach handling exceptions for the server, but at least for the client we probably need to clean up (close connection?) or propagate exception as the request result.The text was updated successfully, but these errors were encountered: