Hi all, I'm a bit late to the party^Wthread, but just wanted to comment that my four repositories are all happy with a connection pool size of 50.
When I ran into "pool exhausted" errors, I triple-checked all usage of the Context class in my custom code and found that there were a couple of cases where I created a new Context instance but never committed or aborted it. Such a Context object will hold on to its DB connection until the object is garbage collected and the connection is released in the finalize method. I also added logging output to the finalize method of the Context class so that I get alerted when a Context object with an open DB connection is garbage collected. cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ 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
