[
https://issues.apache.org/jira/browse/PLC4X-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Z. updated PLC4X-321:
----------------------------
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
was:
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.
> Modbus TCP Timeout not working. NIFI Processor Task gets stuck
> --------------------------------------------------------------
>
> Key: PLC4X-321
> URL: https://issues.apache.org/jira/browse/PLC4X-321
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-Modbus
> Affects Versions: 0.9.0
> Reporter: Martin Z.
> Priority: Major
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
