[PLC4X-321] Modbus TCP Timeout not working. NIFI Processor Task gets stuck

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.0
• Component/s: Driver-Modbus

Language

Java

• Assignee: Unassigned
• Reporter: Martin Z.
• Created: 02/Nov/21 00:48
• Updated: 09/Nov/22 10:20

Description

When using V0.9.0 in PLC4x NIFI-Processor for Modbus TCP, the Processor Task gets stuck, if the network connection is broken. The default timeout and the request-timeout option do not seem to have any affect on this behaviour.

If the NIFI-Processor is started, when the network connection is already broken, a timeout error is thrown. If the connection breaks after a successful initial connection could be made, the running Task gets stuck on the next Modbus TCP Request and has to be forced to terminate.

Using V0.8.0 is working fine in the same scenario with same config in NIFI. In Production, V0.9.0 with Modbus TCP was not usable, since connections broke every day. We had to revert to V0.8.0. This was tested with the PLC4x Build from https://search.maven.org/search?q=plc4j-nifi-plc4x-nar and the official latest NIFI (V1.14.0) Docker and Windows Version