Constant Resetting of CIP connections to AB Control Logix

I am constantly seeing this in the wrapper log and my screen with some “live” tags show tags offline…

INFO | jvm 2 | 2014/05/19 15:33:11 | WARN [TimeoutDaemon ] [15:33:11,071]: [ABControlLogixProcessorStatusRequest] request with key “340” failed due to timeout.
INFO | jvm 2 | 2014/05/19 15:33:11 | WARN [ABControlLogixTransportPool ] [15:33:11,072]: [QC_Robot1] Reseting CIP connection for transaction ID of 340
INFO | jvm 2 | 2014/05/19 15:33:11 | WARN [ABControlLogixTransportPool ] [15:33:11,082]: [QC_Robot1] Reseting CIP connection for transaction ID of 341
INFO | jvm 2 | 2014/05/19 15:33:11 | WARN [ABControlLogixTransportPool ] [15:33:11,083]: [QC_Robot1] Reseting CIP connection for transaction ID of 339
INFO | jvm 2 | 2014/05/19 15:33:11 | WARN [ABControlLogixTransportPool ] [15:33:11,083]: [QC_Robot1] Reseting CIP connection for transaction ID of 338

Including a screenshot of the setup of QC_Robot1 PLC

Any advice on eliminating this issue??

Did you find a solution?

Please let me know solution for this problem.

Those messages are side effects of broken connections. You have to figure out what is making your connections break. Back then, the biggest problem I had with broken device connections was Java Pause-The-World during garbage collection. Which was fixed by using G1GC when it became available. But there are many other possibilities, including too many tags scanning, or too fast.