In Smart Connector - Service Setting - the "Processor Runtime Limit" parameter max value is 3600 seconds, which means 1 hour.
Our discovery processor sometimes may take longer time and currently is is aborted after 1 hour.
Can you change the max value to 36,000?
Processors are supposed to be relatively short lived, so this is by design.
If your processor is supposed to run for a long(or indefinite) time you can implement the ILongRunningProcess interface, which will allow the processor to run until commanded to stop.
Be aware that you have to take great care to make sure that data does not go stale in the DataAdapter(uses EntityFramework behind the scenes) if your processor runs for a long time. Remember this if you run into issues.
Thank you for your quick answer.
This processor discovers all EBO values. If there are many ASPs connected, the time to discover all values might be be long.
Our Discovery processor was initially developed by Jeff Bowman. It is a recursive function.
In addition, the SmartConnector suffers from performance degradation. See my request on June 2021 and your response was:
Thanks for the suggestion! We will add it to our backlog and look into it."
Can you please let me know if this will be addressed in the next version of SmartConnector?
I understand. Then using the ILongRunningProcess interface should resolve your issue.
About the performance when adding a large number of EwsItems to the DataAdapter:
There are additions planned to the API which would allow for batch insertion to the DataAdapter and greatly improve performance for large datasets, but I can't answer when this will be out yet.
As far as I know our processor is using the ILongRunningProcess interface. See below.
[ConfigurationDefaults("EBO OPC Item Discovery Processor", "This processor will search for Items in EBO based on the Discovery Settings configured.")]
public class EboValueItemDiscoveryProcessor : Processor, ILongRunningProcess
Still, when the processor running time reaches the limit, the processor is stopped by SmartConnector.
This should not be able to happen, please provide logs for when this happens.