Re: BUG #12810: database conection drop

"gowridhar.madu@firstdata.com" <gowridhar.madu@firstdata.com> wrote:

> Cannot open ReviewDb
>     at com.google.gerrit.server.util.ThreadLocalRequestContext$1.provideReviewDb(ThreadLocalRequestContext.java:70)

> Caused by: com.google.gwtorm.server.OrmException: Cannot open database connection
>     at com.google.gwtorm.jdbc.Database.newConnection(Database.java:130)

> Caused by: java.sql.SQLException: Cannot get a connection, general error
>     at org.apache.tomcat.dbcp.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:130)

> Caused by: java.lang.InterruptedException
>     at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
>     at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
>     at org.apache.tomcat.dbcp.pool2.impl.LinkedBlockingDeque.takeFirst(LinkedBlockingDeque.java:523)
>     at org.apache.tomcat.dbcp.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
>     at org.apache.tomcat.dbcp.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:358)
>     at org.apache.tomcat.dbcp.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:118)

That Java stack trace looks like the exception is due to a timeout
waiting for a connection.  What is in the database server log from
the same point in time?  Have you perhaps allocated all of the
connections allowed by max_connections and related configuration
settings?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company