shekhartanwar commented on issue #2246: URL: https://github.com/apache/plc4x/issues/2246#issuecomment-3268875769
> Hi, > > yeah ... well you "technically" close it after doing your thing, but it doesn't really close, it but return it to the cache (and potentially waiting threads). In your case I guess you have implemented part of the functionality. I just wanted to make sure that you don't expect the connection to be open indeffinitely. If you're checking things and potentially re-creating connections, you should be fine. But I guess your log output is simply the log of an operation failing and your code then creates a new connection the next time. Hello, I am seeing frequent connection resets with v0.13.1 s7-light driver. It reconnects within 1-2 seconds max, that's why i don't have a problem here, but i can't tolerate frequent connection resets. Please check the logs below. ` 2025-09-09T09:25:41.995+05:30 | 2025-09-09T03:55:41.993Z ERROR 1 --- [oopGroup-1424-1] o.a.p.j.s.c.DefaultNettyPlcConnection : unknown error, close the connection -- | -- | 2025-09-09T09:25:41.995+05:30 | java.net.SocketException: Connection reset | 2025-09-09T09:25:41.995+05:30 | at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(Unknown Source) ~[na:na] | 2025-09-09T09:25:41.995+05:30 | at java.base/sun.nio.ch.SocketChannelImpl.read(Unknown Source) ~[na:na] | 2025-09-09T09:25:41.995+05:30 | at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[netty-buffer-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:356) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:796) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:732) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:658) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998) ~[netty-common-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.123.Final.jar!/:4.1.123.Final] | 2025-09-09T09:25:41.995+05:30 | at java.base/java.lang.Thread.run(Unknown Source) ~[na:na] | 2025-09-09T09:25:41.996+05:30 | 2025-09-09T03:55:41.996Z INFO 1 --- [oopGroup-1424-1] o.a.p.j.s.c.NettyChannelFactory : Channel is closed, closing worker Group also | 2025-09-09T09:25:42.092+05:30 | 2025-09-09T03:55:42.092Z INFO 1 --- [ool-14-thread-1] c.v.p.service.impl.PlcS7Service : Creating PLC Connection... 2025-09-09T09:25:42.092+05:30 | 2025-09-09T03:55:42.092Z INFO 1 --- [ool-14-thread-1] o.a.plc4x.java.DefaultPlcDriverManager : Instantiating new PLC Driver Manager with class loader null -- | -- | 2025-09-09T09:25:42.092+05:30 | 2025-09-09T03:55:42.092Z INFO 1 --- [ool-14-thread-1] o.a.plc4x.java.DefaultPlcDriverManager : Registering available drivers... | 2025-09-09T09:25:42.092+05:30 | 2025-09-09T03:55:42.092Z ERROR 1 --- [ool-14-thread-1] c.v.p.service.impl.PlcS7Service : Plc connect error : Unable to find driver for protocol 's7-light' | 2025-09-09T09:25:42.092+05:30 | 2025-09-09T03:55:42.092Z ERROR 1 --- [ool-14-thread-1] c.v.p.watchdog.impl.WatchdogImpl : Exception occurred while initializing watchdog builder, Message : PLC connection is down | 2025-09-09T09:25:42.093+05:30 | 2025-09-09T03:55:42.092Z ERROR 1 --- [ool-14-thread-1] c.v.p.service.impl.PlcS7Service : Exception occurred while executing write request, Message | 2025-09-09T09:25:42.093+05:30 | java.lang.NullPointerException: null | 2025-09-09T09:25:42.168+05:30 | 2025-09-09T03:55:42.168Z INFO 1 --- [ool-10-thread-1] c.v.p.service.impl.PlcS7Service : Creating PLC Connection... | 2025-09-09T09:25:42.168+05:30 | 2025-09-09T03:55:42.168Z INFO 1 --- [ool-10-thread-1] o.a.plc4x.java.DefaultPlcDriverManager : Instantiating new PLC Driver Manager with class loader null | 2025-09-09T09:25:42.168+05:30 | 2025-09-09T03:55:42.168Z INFO 1 --- [ool-10-thread-1] o.a.plc4x.java.DefaultPlcDriverManager : Registering available drivers... | 2025-09-09T09:25:42.168+05:30 | 2025-09-09T03:55:42.168Z ERROR 1 --- [ool-10-thread-1] c.v.p.service.impl.PlcS7Service : Plc connect error : Unable to find driver for protocol 's7-light' | 2025-09-09T09:25:42.168+05:30 | 2025-09-09T03:55:42.168Z ERROR 1 --- [ool-10-thread-1] c.v.p.watchdog.impl.WatchdogImpl : Exception occurred while initializing watchdog builder, Message : PLC connection is down 2025-09-09T09:25:42.655+05:30 | 2025-09-09T03:55:42.655Z INFO 1 --- [ scheduling-1] o.a.plc4x.java.DefaultPlcDriverManager : Registering available drivers... -- | -- | 2025-09-09T09:25:42.657+05:30 | 2025-09-09T03:55:42.657Z INFO 1 --- [ scheduling-1] o.a.plc4x.java.DefaultPlcDriverManager : Registering driver for Protocol s7 (Siemens S7 (Basic)) | 2025-09-09T09:25:42.657+05:30 | 2025-09-09T03:55:42.657Z INFO 1 --- [ scheduling-1] o.a.plc4x.java.DefaultPlcDriverManager : Registering driver for Protocol s7-light (Siemens S7 (Basic) (light)) ` I can see error like `Unable to find driver for protocol 's7-light'` but in multiple retries it's able to find the driver. I can also observe frequent connection resets throughout the day. This was not the case with 0.12.0 version. Is there anything else can i do here to improve the connection stability? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
