KB-1110 "Pool is Suspended, cannot allocate resources to applications" error printed in the application server log; users are unable to access Appian/business data sources

Parmida Borhani — Mon, 23 Jul 2018 04:01:26 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 4:01:26 AM

Symptoms

The application server is unable to interact with a datasource. If the affected datasource is the Appian datasource, the site may become unresponsive. The following is an example of the server log message found on a Weblogic server:

Feb 18, 2016 9:23:03 AM org.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 0, SQLState: null
    
Feb 18, 2016 9:23:03 AM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: weblogic.common.resourcepool.ResourceDisabledException: Pool AppianPrimaryDS is Suspended, cannot allocate resources to applications..
    
ARNING: SQL Error: 0, SQLState: null
    
    <[ServletContext@624257683[app:suite module:pfdc_sit5 path:null spec-version:3.0]] Servlet failed with an Exception
org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:427)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)
at com.appiancorp.common.config.persistence.ReadWriteConfigurationDaoImpl.getConfig(ReadWriteConfigurationDaoImpl.java:52)
at com.appiancorp.common.config.persistence.ReadWriteConfigurationDaoImpl.containsKey(ReadWriteConfigurationDaoImpl.java:72)
Truncated. see log file for complete stacktrace
Caused By: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1214)
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1147)
at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:1224)
at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:63)
at org.springframework.orm.jpa.DefaultJpaDialect.beginTransaction(DefaultJpaDialect.java:70)
Truncated. see log file for complete stacktrace
Caused By: org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
at com.appiancorp.rdbms.hb.HbSqlExceptionConverter.convert(HbSqlExceptionConverter.java:95)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
Truncated. see log file for complete stacktrace
Caused By: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool AppianPrimaryDS is Suspended, cannot allocate resources to applications..
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:269)
at weblogic.jdbc.pool.Driver.connect(Driver.java:153)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:662)
at weblogic.jdbc.jts.Driver.connect(Driver.java:128)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:589)
Truncated. see log file for complete stacktrace

Cause

There are not enough connections available in the pool based on the following message:

Caused By: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool AppianPrimaryDS is Suspended, cannot allocate resources to applications

The configuration for the maximum connection pool size set for the datasources is insufficent, this prevents the application server from making the required number of connections.

Action

Ensure that the datasoure configuration is using the recommended connection pool size. Please see our documentation for further details: Configuring Relational Databases

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017

Tags: database, infrastructure