ottlukas opened a new issue, #623: URL: https://github.com/apache/plc4x/issues/623
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](https://search.maven.org/search?q=plc4j-nifi-plc4x-nar) and the official latest NIFI (V1.14.0) Docker and Windows Version Imported from Jira [PLC4X-321](https://issues.apache.org/jira/browse/PLC4X-321). Original Jira may contain additional context. Reported by: zedman. -- 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]
