jackxuhaijun commented on issue #2045: URL: https://github.com/apache/plc4x/issues/2045#issuecomment-2760461535
> Indeed this seems to be a common problem with various of our drivers ... gracefully handling disconnects, network problems etc. and allowing a quick recovery. Thank you very much for your prompt reply！ Based on my observations, when using DefaultPlcConnectionManager, a new connection is established after each read operation. In contrast, CachedPlcConnectionManager reuses connections, but if the socket is in the TIME_WAIT state, no communication occurs. In this case, a new CachedPlcConnectionManager needs to be created. However, the old CachedPlcConnectionManager is not properly released, leading to thread leaks and port occupation. If this happens frequently, it can result in too many threads, eventually causing an OOM (Out of Memory) issue. So now I don’t know the best way to use it. Do you have any suggestions? -- 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
