plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject Re: [Netty / S7] Many log messages although everything works
Date Fri, 12 Apr 2019 09:18:37 GMT
But that's not the way you handle logging.

Logging frameworks are built to allow analysis and turn on and off this parts interesting
to me as a user. The way you define what you want is by configuring the logging.

Staying by your car example:
Probably you didn't leave the volume of the stereo at the factory setting ;-) so that's what
we/you have to do to.

Chris

Outlook für Android<https://aka.ms/ghei36> herunterladen

________________________________
From: Julian Feinauer <j.feinauer@pragmaticminds.de>
Sent: Friday, April 12, 2019 11:06:31 AM
To: dev@plc4x.apache.org
Subject: Re: [Netty / S7] Many log messages although everything works

Hi Chris,

well.. thats like the handling procedure if you have an unknown noise in your car... turn
the radio louder __
In this case, I wanted to delete the curse not mute the logs... as It sounds for me this is
a issue to be addressed.

Julian

Am 12.04.19, 11:01 schrieb "Christofer Dutz" <christofer.dutz@c-ware.de>:

    You could increase the log-level ... should reduce the amount of logging drastically.

    Chris

    Am 12.04.19, 10:56 schrieb "Julian Feinauer" <j.feinauer@pragmaticminds.de>:

        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 io.netty.channel.DefaultChannelPipeline
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. 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] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[?:1.8.0_161]
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
~[netty-buffer-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1108)
~[netty-buffer-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:345)
~[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:645)
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580)
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497)
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459)
[netty-transport-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
[netty-common-4.1.23.Final.jar!/:4.1.23.Final] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[netty-common-4.1.23.Final.jar!/:4.1.23.Final] at java.lang.Thread.run(Thread.java:748) [?: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).




Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message