It is uncertain how the deadlocks occur, but it may be application related or due to too many processes running concurrently. To avoid this, all the lookup tables are scheduled to execute every hour. The specific deadlock error message that can occur is as follows:
“Transaction (Process ID #) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. “
When an agent becomes chosen as a deadlock victim, it will go into retry mode. Once it is in this state, it normally does not start again on its own. To correct this error, follow the following steps:
- Stop all agents that have been chosen as a deadlock victim.
- Start each agent one by one. Be sure the agent has started before moving on to the next stopped agent.