KB-1206 "Communications link failure during rollback(). Transaction resolution unknown" error thrown in application server log

Parmida Borhani — Thu, 25 Oct 2018 02:41:17 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/25/2018 2:41:17 AM

Symptoms

The following error is displayed in application server log:

INFO  [stdout] (ajp-/0.0.0.0:8009-14) 2016-07-06 13:16:52,016 [ajp-/0.0.0.0:8009-14] ERROR org.hibernate.util.JDBCExceptionReporter - Statement cancelled due to timeout or client request
WARN  [com.arjuna.ats.jta] (ajp-/0.0.0.0:8009-14) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffac176096:b16e:5776f2fb:4971, node_name=1, branch_uid=0:ffffac176096:b16e:5776f2fb:4975, subordinatenodename=null, eis_name=0 > (org.apache.commons.dbcp2.managed.LocalXAConnectionFactory$LocalXAResource@420114fe) failed with exception code ARJUNA016099: Unknown error code:0: javax.transaction.xa.XAException
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during rollback(). Transaction resolution unknown.

Cause

One of the possible causes is the mismatch of the maximum transmission unit (MTU) between the client and server.

Action

If using Linux, to determine the MTU value, run the following command:

ifconfig

This will display the network interface configurations of the server hosting the database instance, along with the MTU value.

If the Appian instance and database are hosted on the same network, review the MTU settings with your network administrator including any firewalls, proxys, or any other entity regulating the traffic between the servers.

If the Appian instance is hosted on Appian Cloud and the database is being accessed over VPN, please contact Appian Support to assist with the MTU troubleshooting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: administration, network

KB-1206 "Communications link failure during rollback(). Transaction resolution unknown" error thrown in application server log

Parmida Borhani — Thu, 25 Oct 2018 02:41:01 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 10/25/2018 2:41:01 AM

Symptoms

The following error is displayed in application server log:

INFO  [stdout] (ajp-/0.0.0.0:8009-14) 2016-07-06 13:16:52,016 [ajp-/0.0.0.0:8009-14] ERROR org.hibernate.util.JDBCExceptionReporter - Statement cancelled due to timeout or client request
WARN  [com.arjuna.ats.jta] (ajp-/0.0.0.0:8009-14) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffac176096:b16e:5776f2fb:4971, node_name=1, branch_uid=0:ffffac176096:b16e:5776f2fb:4975, subordinatenodename=null, eis_name=0 > (org.apache.commons.dbcp2.managed.LocalXAConnectionFactory$LocalXAResource@420114fe) failed with exception code ARJUNA016099: Unknown error code:0: javax.transaction.xa.XAException
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during rollback(). Transaction resolution unknown.

Cause

One of the possible causes is the mismatch of the maximum transmission unit (MTU) between the client and server.

Action

If using Linux, to determine the MTU value, run the following command:

ifconfig

This will display the network interface configurations of the server hosting the database instance, along with the MTU value.

If the Appian instance is hosted on Appian Cloud and the database is being accessed over VPN, please contact Appian Support to assist with the MTU troubleshooting.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: administration, network

KB-1206 "Communications link failure during rollback(). Transaction resolution unknown" error thrown in application server log

Jordan Horwat — Mon, 23 Jul 2018 17:49:48 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 5:49:48 PM

Symptoms

The following error is displayed in application server log:

INFO  [stdout] (ajp-/0.0.0.0:8009-14) 2016-07-06 13:16:52,016 [ajp-/0.0.0.0:8009-14] ERROR org.hibernate.util.JDBCExceptionReporter - Statement cancelled due to timeout or client request
WARN  [com.arjuna.ats.jta] (ajp-/0.0.0.0:8009-14) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffac176096:b16e:5776f2fb:4971, node_name=1, branch_uid=0:ffffac176096:b16e:5776f2fb:4975, subordinatenodename=null, eis_name=0 > (org.apache.commons.dbcp2.managed.LocalXAConnectionFactory$LocalXAResource@420114fe) failed with exception code ARJUNA016099: Unknown error code:0: javax.transaction.xa.XAException
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during rollback(). Transaction resolution unknown.

Cause

One of the possible causes is the mismatch of the maximum transmission unit (MTU) between the client and server.

Action

To determine the MTU value, run the following command:

ifconfig

This will display the eth0 configurations, along with the MTU value.

To set a new value for the MTU:

ifconfig eth0:0 <IP ADDRESS> netmask 255.255.255.255 mtu <NEW MTU VALUE>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, network

KB-1206 "Communications link failure during rollback(). Transaction resolution unknown" error thrown in application server log

Nick Vigilante — Mon, 06 Mar 2017 20:39:52 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 8:39:52 PM

Symptoms

The following error is displayed in application server log:

INFO  [stdout] (ajp-/0.0.0.0:8009-14) 2016-07-06 13:16:52,016 [ajp-/0.0.0.0:8009-14] ERROR org.hibernate.util.JDBCExceptionReporter - Statement cancelled due to timeout or client request
WARN  [com.arjuna.ats.jta] (ajp-/0.0.0.0:8009-14) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffac176096:b16e:5776f2fb:4971, node_name=1, branch_uid=0:ffffac176096:b16e:5776f2fb:4975, subordinatenodename=null, eis_name=0 > (org.apache.commons.dbcp2.managed.LocalXAConnectionFactory$LocalXAResource@420114fe) failed with exception code ARJUNA016099: Unknown error code:0: javax.transaction.xa.XAException
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during rollback(). Transaction resolution unknown.

Cause

One of the possible causes is the mismatch of the maximum transmission unit (MTU) between the client and server.

Action

To determine the MTU value, run the following command:

ifconfig

This will display the eth0 configurations, along with the MTU value.

To set a new value for the MTU:

ifconfig eth0:0 <IP ADDRESS> netmask 255.255.255.255 mtu <NEW MTU VALUE>

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: network