26.09.2025, 14:19
(This post was last modified: 26.09.2025, 14:53 by EjvindHald.)
I opened the user library and added the single line "log(res, err)" saved and tried again. Then everything worked smooth. Then I commented out that line and it still works fine with immediate reply.
Sorry for all this - I do not know why it did not work before. But it is working fine now. And I am glad that I now know where to add a log statement to gain more info in case of future problems.
Thanks and enjoy your weekend.
Update: after a LM reboot the same faulty behavior came back with only processing one message and then it stops. I will try to get some log info.
I have now tried editing log on and off + reboot, and I cannot find a pattern in the behavior. Only thing is that it generally seems to work better when the log writing is enabled, which makes no sense to me. I cannot go with this, because the log will be flooded with messages, as it issues a timeout message every second.
I never see any error messages in the log. Only many timeouts and now and then processing of a message. See screen shot.
Sorry for all this - I do not know why it did not work before. But it is working fine now. And I am glad that I now know where to add a log statement to gain more info in case of future problems.
Thanks and enjoy your weekend.
Update: after a LM reboot the same faulty behavior came back with only processing one message and then it stops. I will try to get some log info.
I have now tried editing log on and off + reboot, and I cannot find a pattern in the behavior. Only thing is that it generally seems to work better when the log writing is enabled, which makes no sense to me. I cannot go with this, because the log will be flooded with messages, as it issues a timeout message every second.
I never see any error messages in the log. Only many timeouts and now and then processing of a message. See screen shot.