You should try to raise the number of allowed concurrent transactions in both Postgres configuration (max_connections) and DSpace configuration (db.maxconnections).
If you connect to your database and run "SELECT * from pg_stat_activity;" and you see many items as "<IDLE> in transaction", it means all your connections are used up. In particular, this was often caused by the old oai module in DSpace 1.8 and older. You can find more about this error in the archive of this mailing list and in Jira. There isn't really any reliable solution besides raising the number of connections and occasionally restarting Tomcat or upgrading to 3.0. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ 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
