We have this issue as well. Since we don't need the results to be cached on the server side, our current workaround is to quickly timeout the FieldSearch sessions by drastically reducing maxSecondsPerSession.
Doron ---------------------------------------------------------------------- Date: Wed, 26 Sep 2012 15:43:51 +0000 From: "Nguyen, Vincent (CDC/OD/OADS) (CTR)" <[email protected]> Subject: Re: [fcrepo-user] SQL connection not returned to the pool We have the same issue here with our project. I'm interested to hear what the experts have to say Vincent Vu Nguyen -----Original Message----- From: Nicolas Herv? [mailto:[email protected]] Sent: Wednesday, September 26, 2012 11:08 AM To: [email protected] Subject: [fcrepo-user] SQL connection not returned to the pool Hi, I'm having troubles with FindObjects() queries. If I choose to retrieve only the first result of a query : FindObjects findObjectsQuery = new FindObjects().query(query).maxResults(1).pid(); but the query has potentially more than one result, then on the server side the org.fcrepo.server.search.FieldSearchResultSQLImpl is cached for later use. As it keeps the underlying SQL connection, the pool is quickly exhausted. Is there any way to invalidate this object when we explicitly don't plan to access it anymore ? The workaround is to retrieve all results, but it's quite painful. Regards, Nicolas HERVE ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
