KB-2331 How to troubleshoot Database Deadlocks

pauline.delacruz — Tue, 18 Feb 2025 16:51:00 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 2/18/2025 4:51:00 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Database deadlocks occur when two or more transactions are attempting to access the same resource; however neither is able to complete because each transaction is blocking the resource from the other. Additionally any other activities attempting to access the resource will be blocked.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: February 2025

Tags: database, how-to, Performance

KB-2331 How to troubleshoot Database Deadlocks

pauline.delacruz — Tue, 18 Feb 2025 16:50:29 GMT

Revision 13 posted to Appian Knowledge Base by pauline.delacruz on 2/18/2025 4:50:29 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2025

Tags: database, how-to, Performance

KB-2331 How to troubleshoot Database Deadlocks

pauline.delacruz — Tue, 18 Feb 2025 16:50:29 GMT

Revision 14 posted to Appian Knowledge Base by pauline.delacruz on 2/18/2025 4:50:29 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2025

Tags: database, how-to, Performance

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

pauline.delacruz — Wed, 12 Feb 2025 15:20:24 GMT

Revision 12 posted to Appian Knowledge Base by pauline.delacruz on 2/12/2025 3:20:24 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2025

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

pauline.delacruz — Wed, 12 Feb 2025 15:18:09 GMT

Revision 11 posted to Appian Knowledge Base by pauline.delacruz on 2/12/2025 3:18:09 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2025

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

pauline.delacruz — Wed, 12 Feb 2025 15:17:08 GMT

Revision 10 posted to Appian Knowledge Base by pauline.delacruz on 2/12/2025 3:17:08 PM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2025

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Mon, 02 Dec 2024 05:05:10 GMT

Revision 9 posted to Appian Knowledge Base by addam.dinh on 12/2/2024 5:05:10 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Mon, 02 Dec 2024 05:03:47 GMT

Revision 8 posted to Appian Knowledge Base by addam.dinh on 12/2/2024 5:03:47 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Mon, 02 Dec 2024 04:51:38 GMT

Revision 7 posted to Appian Knowledge Base by addam.dinh on 12/2/2024 4:51:38 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------
------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Mon, 02 Dec 2024 04:50:37 GMT

Revision 6 posted to Appian Knowledge Base by addam.dinh on 12/2/2024 4:50:37 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra options" > "Full texts" > "Go"

If there are deadlocks, you should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

If there are no deadlocks, you won't see any competing transactions and will get the default output.

-----------------
BACKGROUND THREAD
-----------------
srv_master_thread loops: 5 srv_active, 0 srv_shutdown, 2092029 srv_idle
srv_master_thread log flush and writes: 2092023
----------
SEMAPHORES
----------

------------
TRANSACTIONS
------------

If there are deadlocks listed in the InnoDB status output

Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Mon, 04 Nov 2024 01:04:30 GMT

Revision 5 posted to Appian Knowledge Base by addam.dinh on 11/4/2024 1:04:30 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Database deadlocks occur when two or more transactions are waiting for one another to give up their locks. This means that two or more entities are blocking some sources, and none are able to finish as they are blocking the sources in a cyclical manner.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra Options" > "Full Text" > "Go"

You should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

This confirms that the site is encountering deadlocks

4. Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Fri, 01 Nov 2024 04:05:22 GMT

Revision 4 posted to Appian Knowledge Base by addam.dinh on 11/1/2024 4:05:22 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you have to select "Full Text" to find details of the latest deadlock.

Go to "Extra Options" > "Full Text" > "Go"

You should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

This confirms that the site is encountering deadlocks

4. Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Wed, 28 Aug 2024 04:16:52 GMT

Revision 3 posted to Appian Knowledge Base by addam.dinh on 8/28/2024 4:16:52 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you may need to scroll up to find details of the latest deadlock.

You should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

This confirms that the site is encountering deadlocks

4. Identify the details of both transactions in the deadlock

Date and Time of the latest deadlock (US local time)
Thread ID
Query ID
Query details

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Wed, 28 Aug 2024 02:06:35 GMT

Revision 2 posted to Appian Knowledge Base by addam.dinh on 8/28/2024 2:06:35 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you may need to scroll up to find details of the latest deadlock.

You should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

This confirms that the site is encountering deadlocks

4. Identify the details of both transactions in the deadlock

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.

[DRAFT SP-411] KB-XXXX How to troubleshoot Database Deadlocks

addam.dinh — Wed, 28 Aug 2024 02:05:51 GMT

Revision 1 posted to Appian Knowledge Base by addam.dinh on 8/28/2024 2:05:51 AM

Purpose

This article details how to identify and remediate MariaDB database deadlocks in Appian.

Note: This KB is for customers with Appian Cloud Maria DB. Customers with self-managed databases will need to contact their Database Administrator.

Symptom

You can identify database deadlocks from tomcat-stdOut.log in the <APPIAN_HOME>/logs directory.

Error details: Deadlock found when trying to lock; try restarting transaction

Caused by: org.springframework.dao.DeadlockLoserDataAccessException... Deadlock found when trying to get lock; try restarting transaction..

Instructions

As a user with Database Administrator privileges, access the Cloud Database through the navigation menu.
In phpMyAdmin, navigate to the Appian database using the Databases tab in the toolbar.
View the InnoDB status by running the following stored procedure:

CALL AppianProcess.showEngineInnodbStatus()

The output of this stored procedure will be quite large, so you may need to scroll up to find details of the latest deadlock.

You should see two competing transactions listed as deadlocks.

------------------------
LATEST DETECTED DEADLOCK
------------------------
YYYY-MM-DD HH:MM:SS <DEADLOCK_ID>
*** (1) TRANSACTION:
<TRANSACTION_DETAILS>

*** (2) TRANSACTION:
<TRANSACTION DETAILS>

This confirms that the site is encountering deadlocks

4. Identify the details of both transactions in the deadlock

If there are no deadlocks listed in the InnoDB status output

Try the following stored procedures to see other types of database locks

CALL AppianProcess.databaseLocks()
CALL AppianProcess.metadataLocks()

Affected Versions

This article applies to all versions of Appian.