DSpace 1.7.1
psql 8.4.12
We are occasionally seeing the following error message in our DSpace cocoon
logs ...
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
pool error Timeout waiting for idle object
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
at
org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:588)
at org.dspace.core.Context.<init>(Context.java:95)
at
org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:72)
at
org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:53)
at
org.dspace.app.xmlui.cocoon.BitstreamReader.setup(BitstreamReader.java:169)
... 66 more
I'm wondering these can be alleviated by increasing the database connection
pool size but I'm not sure how to do that. Would that be done somewhere in the
DSpace application (if so, where) or would it be something done at the psql
level?
Thanks.
--Jim
Jim Coble
Information Technology Services
Perkins Library, Duke University
Box 90196, Durham, NC 27708
919-660-5974 (voice); 919-668-2578 (fax)
[email protected]<mailto:[email protected]>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
