plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Feinauer <>
Subject [Netty / S7] Many log messages although everything works
Date Fri, 12 Apr 2019 08:56:27 GMT
Hi all,

as many of you may know, we use PLC4X pretty heavily in Prod.
We recently checked our logs and found a lot of entries from PLC4X which are thrown although
everything is working.
This is something I want to fix (if theres no issue then be silent).
We use the S7 driver, but I think this is a general Netty (tcp?) topic.

The mostly logged issue is thrown logged by and is

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.
Die Verbindung wurde vom Kommunikationspartner zur├╝ckgesetzt at
Method) ~[?:1.8.0_161] at ~[?:1.8.0_161]
at ~[?:1.8.0_161] at
~[?:1.8.0_161] at ~[?:1.8.0_161]
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(
~[netty-buffer-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.buffer.AbstractByteBuf.writeBytes(
~[netty-buffer-4.1.23.Final.jar!/:4.1.23.Final] at
~[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at$
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$
[netty-common-4.1.23.Final.jar!/:4.1.23.Final] at
[netty-common-4.1.23.Final.jar!/:4.1.23.Final] at [?:1.8.0_161]

Could anyone comment on that, what this means or what we can / should do to handle this?
We get this entry nearly 100 times a hour (for multiple hundreds requests).
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message