Thanks, helix84: Yes, I switched things back to 100 for max connections. It looked like increasing the connections didn't really solve the problem. The odd thing is that everything was fine for a long time until this weekend. The amount of hits is heavy, but it isn't unusual. So, right now, I'm stumped. I did do the tomcat and postgres restarts, but it doesn't really help. George Kozak
On Mon, Nov 14, 2016 at 11:52 AM, helix84 <[email protected]> wrote: > And by the way, increasing max connections may prolong the runtime > slightly, but is not ultimately a solution, the transactions will leak > nevertheless. 500 max connections is probably way too many for DSpace. I > would definitely not go higher than 100. > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > -- *************************** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 [email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
