KB-1943 The application server fails to start with a "Too many connections" error thrown in the application server log

Parmida Borhani — Thu, 23 May 2019 23:43:00 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 5/23/2019 11:43:00 PM

Symptoms

The application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

The application server will throw this error when attempting to connect to the database server, and all available connections are in use by other clients. More information regarding this database error can be found in the MySQL documentation.

Action

Set the max_connections variable to a larger value. For MySQL, this can be done without having to restart the database. Refer to the respective database documentation for the exact steps on how to perform this action on the database server.
Restart the database server which will reset the connections if you wish to not increase the max_connections variable.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2019

Tags: database, application server, infrastructure

DRAFT KB-XXXX The application server fails to start with a "Too many connections" error thrown in the application server log

Parmida Borhani — Thu, 23 May 2019 23:39:03 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 5/23/2019 11:39:03 PM

Symptoms

The application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Set the max_connections variable to a larger value. For MySQL, this can be done without having to restart the database. Refer to the respective database documentation for the exact steps on how to perform this action on the database server.
Restart the database server which will reset the connections if you wish to not increase the max_connections variable.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2019

Tags: database, application server, infrastructure

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Parmida Borhani — Thu, 23 May 2019 23:38:31 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 5/23/2019 11:38:31 PM

Symptoms

The application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Set the max_connections variable to a larger value. For MySQL, this can be done without having to restart the database. Refer to the respective database documentation for the exact steps on how to perform this action on the database server.
Restart the database server which will reset the connections if you wish to not increase the max_connections variable.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2019

Tags: database, application server, infrastructure

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Tejas Kargutkar — Thu, 02 May 2019 14:49:04 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 5/2/2019 2:49:04 PM

Symptoms

Application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Set the max_connections variable to a larger value. For MySql, this can be done on the fly without having to restart the database. Refer to the respective database documentation for the exact steps on how to perform this action on the database server.
Restart the database server which will reset the connections if you wish to not increase the max_connections variable.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Jordan Horwat — Mon, 22 Apr 2019 20:48:42 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 4/22/2019 8:48:42 PM

Symptoms

Application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Restart the database. This will reset the connections and allow Appian to connect to the database.
If this is a recurring issue, the database team may want to set the max_connections variable to a larger value. Please refer to the respective database documentation on how to perform this.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Jordan Horwat — Mon, 22 Apr 2019 20:48:31 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 4/22/2019 8:48:31 PM

Symptoms

Application server fails to start with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Restart the database. This will reset the connections and allow Appian to connect to the database.
If this is a recurring issue, the database team may want to set the max_connections variable to a larger value. Please refer to the respective database documentation on how to perform this.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Tejas Kargutkar — Mon, 22 Apr 2019 19:38:35 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 4/22/2019 7:38:35 PM

Symptoms

Application server fails to start up with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
.
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

The application server will throw this error when attempting to connect to the database server, all available connections are in use by other clients. This documentation can be used as a reference for more details on this database error.

Action

Restart the database which will reset the connections and allow Appian to connect to the database.
If this is a recurring issue, then the database team may want to set max_connections variable to a larger value. Please refer to the respective database documentation on how to perform this.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Tejas Kargutkar — Mon, 22 Apr 2019 19:36:56 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 4/22/2019 7:36:56 PM

Symptoms

Application server fails to start up with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
.
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

Restart the database which will reset the connections and allow Appian to connect to the database.
If this is a recurring issue, then the database team may want to set max_connections variable to a larger value. Please refer to the respective database documentation on how to perform this.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Tejas Kargutkar — Mon, 22 Apr 2019 19:31:16 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 4/22/2019 7:31:16 PM

Symptoms

Application server fails to start up with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
.
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

The database administrator may increase the max connections value.
If increasing the value to a higher number is not warranted, then the database team may perform a database restart which will reset the connections and allow Appian to connect to the database.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss

DRAFT KB-XXXX Jboss/Tomcat fails to start with "Too many connections" error in the application server log

Tejas Kargutkar — Fri, 19 Apr 2019 17:51:23 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 4/19/2019 5:51:23 PM

Symptoms

Application server fails to start up with the following error observed in the application server log:

ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: jdbc/AppianPrimaryDS (Could not create connection): javax.resource.ResourceException: Could not create connection
	at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:522)
.
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: "Too many connections"

Cause

Action

The max connections value can be increased to a higher value.
A database restart can reset the connections which will allow Appian to connect to the database.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: Tomcat, database, application server, infrastructure, jboss