procedure usp_getnextcase, line 195, message: Failed to get app lock for work queue item

[HumbertoIgnacio]

Hi All,

On the last few weeks i have been severed by this two problems, thats happens in a lots of resources in running time.

Reason: Internal : Retries 6, The statement or function must be executed in the context of a user transaction.
error 51000, level 16, state 1, procedure usp_getnextcase, line 195, message: Failed to get app lock for work queue item

System.IO.IOException: Cannot write data to transport connection: An established connection was aborted by software on the host computer. ---> System.Net.Sockets.SocketException: An established connection was aborted by software on the host computer in System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) in System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) --- End of internal exception stack trace --- in System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) in BluePrism.AutomateAppCore.clsListener.ListenThread()

We have a environment with 211 resource machines, the half suffers from this issue. The application server has 3 nodes and one database.

We have applied the best pratices in Tags, but the problem still persists.

Could someone land a hand on that please ?

Kind regards

[JerinJose]

Hi Humerto,

what is the latency between the RR and server? if its >20-50 millisecond this connection drops will be frequent. Also check the event logs in application server for the same timestamp. It will help you understand if there is some issues in writing data to the database,
since you have a pretty large Bot farm there is a chance that the database size is growing exponentially, that could cause performance issues like this

[HumbertoIgnacio]

All the logs are off due the size growning from database, and we run a script every night to clear data older then 2 days, to maintain performance. This process consumes 11k itens per day. Throughout the year we had this issue only 2 times, in the case of System.IO Exception, for the getnextcase exception this is the first time.
The database has not been alter, neither the servers...