You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@plc4x.apache.org by "Lukas Ott (Jira)" <ji...@apache.org> on 2020/07/23 19:19:00 UTC

[jira] [Commented] (PLC4X-127) Uncaught exceptions from the Netty Pipeline

    [ https://issues.apache.org/jira/browse/PLC4X-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163897#comment-17163897 ] 

Lukas Ott commented on PLC4X-127:
---------------------------------

[~julian.feinauer] What is the status here? Is this bug still relevant for Version 0.6 / 0.7+?

> Uncaught exceptions from the Netty Pipeline
> -------------------------------------------
>
>                 Key: PLC4X-127
>                 URL: https://issues.apache.org/jira/browse/PLC4X-127
>             Project: Apache PLC4X
>          Issue Type: Bug
>    Affects Versions: 0.4.0, 0.3.1
>            Reporter: Julian Feinauer
>            Priority: Major
>
> When using in production for long times.. we often times get this WARN from Netty.
> This should be adressed and handled properly.
> {code:java}
> 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: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
> at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_161]
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:1.8.0_161]
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:1.8.0_161]
> at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_161]
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)