Hello We are using stored procedures and it's executed by auto processe

prasadhk over 10 years ago

Hello
We are using stored procedures and it's executed by auto processes that executes every few minutes. Sometimes the DB node throws the error "com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Write connection. Safe to retry. ". If we manually reexecute the node, it works just fine. Do anybody come across this issue? Currently the pool size is set to 5000 in our appian ds xml. If we increase the pool size, that would help to resolve this? any thoughts? Is there a way we retry the DB node if this error occurs?...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

As Matt mentions, this error indicates that the engines where busy to respond in time to the request that this smart service did. There are several areas of the product that will retry when this error occurs, but query rules, write to DS and query DB nodes do not offer a retry logic for this error. That is why restarting the node works.

In this case you may want to move these processes that are failing to times where the engines are not checkpointing nor experiencing heavy load. For instance, let's say you know that every day at 7AM you have a lot of automated/scheduled processes to run, and then you realize that your stored procedures in a different model fail around this time. At this point the solution is to re-schedule those automated process to run outside business hours for example.

An enhancement request has been created to support a retry logic in these nodes when the engines are busy to respond to the request. The reference number is AN-40499

Eduardo Fuentes
Appian Technical Support
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

As Matt mentions, this error indicates that the engines where busy to respond in time to the request that this smart service did. There are several areas of the product that will retry when this error occurs, but query rules, write to DS and query DB nodes do not offer a retry logic for this error. That is why restarting the node works.

In this case you may want to move these processes that are failing to times where the engines are not checkpointing nor experiencing heavy load. For instance, let's say you know that every day at 7AM you have a lot of automated/scheduled processes to run, and then you realize that your stored procedures in a different model fail around this time. At this point the solution is to re-schedule those automated process to run outside business hours for example.

An enhancement request has been created to support a retry logic in these nodes when the engines are busy to respond to the request. The reference number is AN-40499

Eduardo Fuentes
Appian Technical Support
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data