atomikos / transactions-essentials

Development repository for next major release of
https://www.atomikos.com/Main/TransactionsEssentials
Other
461 stars 139 forks source link

Connection pool exhausted - try increasing 'maxPoolSize' and/or 'borrowConnectionTimeout' on the DataSourceBean. #172

Open fmzhu opened 2 years ago

fmzhu commented 2 years ago

Connection pool exhausted - try increasing 'maxPoolSize' and/or 'borrowConnectionTimeout' on the DataSourceBean. we are using the atomikos through "spring-boot-starter-jta-atomikos" with version 2.6.11, wenn the spring boot application runs after a while, we get the "Connection pool exhausted"- try increaing 'maxPoolSize' and/or 'borrowConnectionTimeout' on the DataSourceBean." Exception, the configuration from "Connection pool" ist "1", after Communication with Database Team, wir cannot change the Connection Pool Size into more than 1, has someone the same issues, thanks very much in advance!

Die Stack Trace:

Caused by: com.atomikos.jdbc.AtomikosSQLException: Connection pool exhausted - try increasing 'maxPoolSize' and/or 'borrowConnectionTimeout' on the DataSourceBean. at com.atomikos.jdbc.AtomikosSQLException.throwAtomikosSQLException(AtomikosSQLException.java:29) at com.atomikos.jdbc.AbstractDataSourceBean.throwAtomikosSQLException(AbstractDataSourceBean.java:76) at com.atomikos.jdbc.AbstractDataSourceBean.throwAtomikosSQLException(AbstractDataSourceBean.java:71) at com.atomikos.jdbc.AbstractDataSourceBean.getConnection(AbstractDataSourceBean.java:351) at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:38) at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:108)

MarcinGil commented 1 year ago

I have had very similar issue - however the true problem was bad password! This exception/error is very very misleading.

GuyPardon commented 1 year ago

Good point, thanks for the feedback!