Unable to acquire a Read connection. Safe to retry.

RE: Unable to acquire a Read connection. Safe to retry.

sushilk17 — Tue, 29 Nov 2016 06:14:03 GMT

@kaushikr735, are you able to find the solution for mention issue ?

RE: Unable to acquire a Read connection. Safe to retry.

kaushikr735 — Wed, 28 Sep 2016 14:07:01 GMT

@sumeetk @sanjays Thanks for you reply. We had opened the Appian case and we got reply that
"This happens when application server is unable to communicate with the engines (in this specific case, it seems to be the execution engines).
Reasons for this can vary, but commonly include network or connectivity issues between the servers in a distributed installation, or very high resource utilization (such as high heap, memory, and/or cpu)."

RE: Unable to acquire a Read connection. Safe to retry.

sanjays0006 — Fri, 23 Sep 2016 20:53:34 GMT

Adding to sumeet's comment, check your server performance as well.
We got this error when there is a very high memory usage on Appian server.
Check your server memory once and do the necessary clean up.

RE: Unable to acquire a Read connection. Safe to retry.

Sumeet Khare — Fri, 23 Sep 2016 19:55:28 GMT

this issue can be due to following possibilities:
1 - the cdt which you are using for converting it to xml has hugh amount of data and the conversion is failing.
2 - KDB's are heavily loaded when that code is getting executed. This can happen due to parallel activities going.