[
https://issues.apache.org/jira/browse/PLC4X-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271114#comment-17271114
]
Christofer Dutz commented on PLC4X-127:
---------------------------------------
Is this still an issue? If not, I'd probably close it in favor of adding more
concrete issues for actual problems (This description is so vague, that it
makes it allmost impossible to start working on this issue)
> 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)
