Binding Modbus 2.5.7. Stops working after unsuccessful read attempt

[ssalonen]

@stfn82

Edit: After changing something in my thing this error comes up, after which the binding starts to work. Still a NPE is not good I guess:

What do you mean? I do not see any NullPointerException (NPE).

@BHall I do not understand what you are trying to say with the log levels … Sounds you can reproduce the polling issue by changing log level? That’s great if that is the case – we can use that to troubleshoot it faster. I did not manage to do this myself with simple setup so there must be more to it.

Both @BHall & @stfn82: when the polling stops, please follow the advice set in this post

Modbus stops without any errors

Do you have full logs to send me please? how does the last success item update? Does it stop updating? how does the last error item update? Does it stop updating? Can you also execute the following two commands in karaf console when the polling stops threads --locks --monitors and threads The output of those commands should help to understand what the binding is doing.

i.e.

Please execute the following two commands in karaf console when the polling stops

threads --locks --monitors

and

threads

Looks like logs are not helping much at the moment… All I can say is that it looks that there is some sort of deadlock happening somewhere in the binding.