marcschier
commented
3 months ago Unfortunately the OPC UA stack logs the exception, which actually are just indications of the service result status of the last publish request (since subscriptions are active). I cannot disable the error logs from the stack, and that unfortunately includes the exception stack trace.
The problem with MQTT transport is that the MQTT RPC call hangs forever on the reconnect (#2213), but the HTTP call should actually respond with error (at least after a while). Is this the case @NoTuxNoBux ?
Describe the bug Sending a command to an OPC UA server the publisher 2.9.4 is connected to, and the connection unexpectedly dropping (the machine stopped responding) resulted in the publisher getting into a permanent exception state where it spams the same exception every time.
This has the same result as and might be related to #2189, but is caused in a different way.
To Reproduce I can't always reproduce this in the exact same fashion, but this is what happened:
Expected behavior The publisher recovers and treats the connection to the server as disconnected, trying to reconnect (and not throw exceptions).
Additional context Logs of what happened when I sent the command (beginning), resulting in the exceptions (end):