Could you verify if other Data calls to the PIServer are also blocked?
We have recently identified a potential issue that may cause the behavior you are seeing, which was related to the locking in connection check/reconnection logic in our internal library, hence all RPCs made to the PIServer are blocked. This will be fixed in the upcoming AF SDK 2.6 patch release (i.e. 2.6.1.x).
Just to confirm what Eddy said, or maybe you have already seen our PI System Roadmap, we're in the midst of preparing for an AF 2.6.1 service pack. Are you seeing this behavior with PI AF 2014 (v2.6)?
I am using OSIsoft.AFSDK.dll 22.214.171.12443
I have a recovery thread that re-attempts the blocking operation.
The recovery threads block too.
When will this patch be available?
Based on PI System Roadmap, the expected time of delivery is Q3 2014
Is there any graceful work around?
The trouble I have now is the only way to fix the problem is to restart the process.
This is a nuclear option in a system which we are deploying for field tests this week.
(meaning Q3 is too far away for us).
Are you already using PIBufss? If you pass off the writes to PIBufss it will handle the re-connection within it's own context leaving you free to handle recovery (like re-creating your objects & connection). Unless the lock happens before AF SDK passes the events to PIBufss. Just a thought.
I am assuming that PIBuffss is used automatically when I make the UpdateValues call.
If it is not used automatically then I need to use it because my system depends on that capability.
How do I confirm that PIBufss is being used?
Hi Randy, if security is properly configured for PIBufSS and PIBufSS service is running then writing through AF (2.6) will by default utilizes PIBufSS. You can get doc on how to configure PIBufSS from techsupport download page, or feel free to call tech support if you need help to properly configure it.
To confirm that PIBufSS is being used, the easiest way is, in PSE that comes with AF 2.6, the server connection dialog contains Buffer Status information.
Note that one of the downsides in using PIBufSS that comes with the release AF 2.6.0 is that it can only buffer to one PIServer, or only buffer/fan to only one PICollective. The upcoming PIBufSS that will come with AF 2.6.1 patch release does not have this limitation.
In your recovery thread, did you try to disconnect/reconnect from the piserver prior to re-trying the Data call?
But again, I'd highly recommend that you try to upgrade if possible.
Retrieving data ...