Hello,

I do not understand how the following two statements can go together:
"The console application blocks at the constructor call of the second client."
"The strange fact is that if I create two (not one, two) clients in the program's main function then the application won't block.".

So, if you create two clients, according to the first sentence, it blocks; according to the second sentence, it does not block. Can you clarify? Or does it have to do with the fact *where* you create them? (in the main function, versus the threads?)

There was no fix to specifically address this issue, because, in general, we can only fix issues that we can reproduce. But we do not provide fixes for earlier versions, so the first thing to do would be to try the behavior with the newest version (2018.1). If that fixes the problem and you are not covered by the maintenance, I can give you an additional discount towards purchasing an upgrade. If using 2018.1 does not fix it, I would ask you to kindly try to put together an example that we can run on our side and that shows the problematic behavior.

Best regards

Thank you.

This sounds similar to the problem I have described earlier. I think we should try some workarounds.

Can you pre-create the objects in the main thread, and then just use them? EasyDAClient allows
that.

Or, based on how you have described your needs, why don't you just create one EasyDAClient instance and use it in all threads? That is also allowed.

Best regards

Can you describe what precisely happens? Does the first creation of EasyDAClient block? Or does the second block? Or some subsequent creation? If it does, does it block forever, or does it just take very long time? Is the behavior always precisely the same, or are there variations?