> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Edwin van der Elst > > There was a bug in the connectionpooling code in 1.6.x (which > was fixed back then). The problem was that prepared > statements where closed, but NOT the ResultSet. This should > be ok according to the jdk api-doc, but with postgres, this > resulted in a resource leak. > > Maybe, somewhere else in the code, resultsets are not closed, > resulting in this kind of errors.
Correct. I remember fixing this in both 1.6 an 1.7 branches by reviewing all pieces of code containing the word "ResultSet". Since then new code may have introduced new resultsets that are not closed. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED]
