What is the expected behavior when using ‘Execute One Now’ on an additional (virtual) protocol thread that’s only used for something like message processing?
The virtual protocol thread only has a queue with no timers, etc.
Does this mean that the ‘Execute One Now’ and ‘Execute One’ basically result in the same behavior as there are no timers?
Can the ‘Execute One Now’ even be used on a protocol thread with no timers?
We’ve noticed they’re not acting in the same way with a ‘virtual’ protocol thread as the ‘one’ operation isn’t taken into account for the ‘Execute One Now’ as it’s adding the same group multiple times to the queue. Whilst the ‘Execute One’ does take the ‘one’ operation into account.
https://docs.dataminer.services/develop/devguide/Connector/Actions/ActionExecuteOne.html
Hi Brecht,
I would expect them to behave the same regardless of which protocol thread they are executed on. So if you have particular cases we can investigate and improve, please send us a task with the details.
That being said, we did resolve some problems with the multiple protocol threads, especially when using SNMP polling. RN36441 will be released in 10.3.9 and the MRs. Feel free to contact me if you want to test against this version.