On Thursday, February 8, 2018 at 6:09:35 AM UTC-5, Kosmas Kaifel wrote:
> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a
> connection, pool error Timeout waiting for idle object
It is possible that your connection pool is too small for the load on the
service, or that the DBMS has its connection limit set too low. It is also
possible that you have connections which become unusable (typically "idle
in transaction"). The first step is to figure out which condition is
causing the pool to time out.
If you are using PostgreSQL for your DBMS, then each connection is
represented by a separate process on the DBMS host, and the process'
description is set to show the state of the connection.
https://www.postgresql.org/docs/9.2/static/monitoring-ps.html may be
helpful. You may find other messages in the DSpace log that give more
information. Something like the 'netstat -t' command, run on the DSpace
host, can show you how many client connections are open from that host.
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.