I would think you’d want to handle it, and then investigate the reason for
it in this instance
On April 12, 2019 at 08:51:05, Christofer Dutz (christofer.d...@c-ware.de)
wrote:
Hi Otto,
I think the English translation would be something like:
"Connection reset by remote" or "Connection reset by peer"
Not sure if this helps understand what's going on ... I always thought it
was related to
the PLC hanging up without following the correct procedure for doing that.
Sort of like
just hanging up the phone without saying goodbye.
Perhaps really implementing an exception handler and just swallowing the
exception
Because we know we're operating in "unpolite" environments ... but not sure
what
We could do to gracefully handle the situation.
@Julian ... would it be ok to catch that and simply log an "INFO" severity
message ("Remote hung up unexpectedly")
Chris
Am 12.04.19, 13:52 schrieb "Otto Fowler" <ottobackwa...@gmail.com>:
The netty handlers don’t implement exceptionCaught so the default is to
spew to logs. I don’t speak german so I don’t know what the exception
message is.
Maybe the handlers should implement the method.
On April 12, 2019 at 04:56:40, Julian Feinauer (j.feina...@pragmaticminds.de)
wrote:
An exceptionCaught() event was fired, and it reached at the tail of the
pipeline. It usually means the last handler in the pipeline did not handle
the exception. java.io.IOException
