Will investigate. Do not send further call stacks until further notice. Analyzing each of them is hours worth of work.

Will investigate.

I have made a change in which unexpected conditions while disconnecting should not result in a hang. This is, however, not a proper solution, because I still do not know what this unexpected condition might have been. But it is worth trying, being the best I can offer at this moment.

The fix is is in the latest QuickOPC 2019.2, build 5.56.1055.1 or later.

Regards

We will prepare a new (patched) build and and I will make a new post here when it is ready. There currently isn't a useful logging we can turn on; debug symbols could be useful if we knew what the original cause was, but not that much at the point of hang, as for that moment the information I have from the call stack is enough .

The item counts are quite high. In any case (independent of the fix), I recommend that you also do this:These are all static parameters on the EasyDAClient class that need to be set once, before a first instance of it is created.

Best regards

Hello.

I have analyzed the call stacks. I do not see a true deadlock (two locks taken on two threads in reverse order). But most of the threads seem to be waiting for a "disconnect to happen on a particular server, and I do not see the thread that should be "working" on the disconnect. So in that sense, it is understandable that things get blocked.

But the question is, where is the thread that should have been working on the disconnect? It looks like that it is gone before it had a chance to notify the other thread (that is waiting on it) that the disconnect has been finished. I do not know the reason for that. I can guess that it has abnormally terminated - and that would be the true issue that we need to hunt. I am thinking that, just as a precaution, maybe I can add some code that would assure that the waiting thread is always notified. Need to think this through.

A question: How many items are you dealing with, roughly?

Regards

I started to work on it but got distracted; it is complicated and needs uninterrupted to focus on. I hope to do continue on it over this coming weekend.