I am using system.tag.queryTagHistory() to query an OPC-HDA provider.
Everything is working fine, but when the dataset gets to big, the function times out, which is OK.
I have included the argument timeout like this:
If is set timeout to 10000 msec, it will timeout at 10s. My problem is that i cannot change the timeout higher than 60000.( It will still timeout at 60s if I set 100s.)
Further, I have set the project property client timeout to 100, saved and re-launched the client. Still no timeout higher than 60s. (see picture below).
Im currently using 8.06, and is pulling the history through a remote history provider (gateway network).
Any ideas anyone?
Any possibility your DB is imposing its own timeout?
Not sure @pturmel, It looks like the timeout comes from the ignition connector based on the message below…
Further, The query size is only at 32000 records, and normally we are limited to 150k from other systems. To begin with, we can atleast state that the Ignition driver is a bit slow.
com.inductiveautomation.metro.api.ex.TimeoutExpiredException: TimeoutExpiredException[queueId=service_TagHistoryService, targetIntent=_services.invoke_|2, msgData=com.inductiveautomation.ignition.gateway.sqltags.history.distributed.TagHistoryService#queryTagHistory([interface com.inductiveautomation.ignition.common.sqltags.history.TagHistoryQueryParams])]
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
I have a feeling there is a bug in the client read timeout in Ignition 8. If I run queryTagHistory() from a reporting scheduled script, it might run for 5 minutes without timeout. So maybe there is something about the client / designer scope.
Hmm, looks like you’re querying against a remote provider, and the timeout is occurring at the gateway network service level…
Ugh, looks like gateway network service invocations are hardcoded at 60s timeout right now…
Oh… Thats to bad. Thanks for the reply anyways!
I will have to wait for the patch, and then for sepasoft OEE to release their stable build for that version
@Kevin.Herron any updates on the hardcoded 60s?
Hi @Kevin.Herron, do you have any update about this topic?
Nothing has changed, the ticket is in “incubation”…
If you want to contact a support rep and explain your setup and why this is a problem for you that will help. Reference IGN-3005 as the ticket number.