This particular message may not be necessarily related to Web API itself.
Are you using HttpClient?
If so, you may want to check your timeout property,
Check if the request before this, happened around 100 seconds (or the timeout property you set) before it?
Thanks Justin. Yes, we are using HttpClient to make the connections.
We had observed that when PI web API under high stress/load, things are getting slower to return progressively till we hit this task canceled exception.
the 1st 10 calls - taking 5 seconds to return
the next 10 calls, taking 10 seconds to return
the next 10 calls, taking 30 seconds to return
the next 10 calls, taking > 30 seconds
We are not sure if increasing timeout in this scenario is the right thing to do. Or we just need some help to review the server settings or SQL PIFD ?
We use PI Web API extensively in our architecture.. and we are struggled with what we are experiencing. Will this be fixed in 2017 version (latest release with the hot patch we are anticipating) ? Or this is completely a diff thing?
Other users reported the same issue?
Hi, Should I open a case with tech support on this? Would like to know if there anything we could do on the server settings for the PI Web API to be able to handle high load. Thanks!
Yes, this behavior (operation canceled) is a completely different thing than your case 865959. It is not necessary a PI Web API related problem or a bug either.
We have seen only one customer reported this issue.
We couldn't find the root cause at the beginning.
However, this customer later told us that they were performing online PI Data Archive reprocessing on a daily basis, which is not a common operation.
Maybe you can start checking with the PI AF admin and PI Data Archive admin to see if there are indeed some resource intensive operation is going.