We have a virtual connector that's running nothing but queries via SLScripting.
We do however want the element to reflect on whether those queries keep working or not.
This by putting the element in and out of timeout depending on the fact whether or not the queries are continuously failing or not (similar to DataMiner's automatic element timeout behavior).
We're trying to achieve this by using the Change_Communication_State notify.
We've tried both the local and remote options and even tried using both the connection ID as -1 or 0, but the outcome remains the same:
- Putting an element into a responding (= non timeout) state always happens immediately, no delay whatsoever.
- Putting an element into a timeout state always goes with the default delay of 30 seconds before the element actually shows the timeout.
Is there any way to put a virtual standalone element immediately into timeout without having to wait for the element's default timeout setting delay?
Hi Brecht,
Thank you for your question! I would like to start by stating that the behavior you describe is according to how it's documented.
I'm personally not aware of a way to put the element in timeout directly.
However, rather than having a possibility to set the element in timeout right away, I would personally be more in favor of having a way to configure in the protocol.xml if the element timeout settings should be shown or not within the element edit wizard.
This way, users can configure how long the element has to stay without any succesfull communication before going into timeout, just like for any other connector. This way, behavior will be completely in line with other more classic connectors and there is no need to reimplement similar logic in all connectors (no need to reinvent the wheel).
Hope this helps.
regards,