JoelGaechter opened a new issue, #2418: URL: https://github.com/apache/plc4x/issues/2418
### What happened? I recently updated from version 0.13.0 to 0.13.1, and encountered an issue where my device would time out when another device establishes a connection. My setup consists of four devices connected through Modbus TCP, whereas three of them are turned on by the other one. A single `CachedPlcConectionManager` is used for all connections and each one has a read-write loop running in a separate thread. If an exception occurs in the loop, the connection is removed from the cache using `CachedPlcConnectionManager::removeCachedConnection`. Initially, the loop would only succeed for one device until this switches on the others. Previously the others would also start communicating seamlessly, but now the former has a hiccup at this point, which in my case causes it to timeout and switch off the others again. In my understanding the connections should be decoupled and not influence each other. Was there anything introduced that could cause the connections to interfere with each other during reading, writing, or connecting ### Version v0.13.1 ### Programming Languages - [ ] plc4c - [ ] plc4go - [x] plc4j - [ ] plc4net - [ ] plc4py ### Protocols - [ ] AB-Ethernet - [ ] ADS /AMS - [ ] BACnet/IP - [ ] C-Bus - [ ] CANopen - [ ] EtherNet/IP - [ ] Firmata - [ ] IEC-69870 - [ ] KNXnet/IP - [x] Modbus - [ ] OPC-UA - [ ] Profinet - [ ] S7 - [ ] S7-light -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
