> > -----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.
I just performed a similar search inside org.mmbase.storage and there are multiple locations where ResultSet is not closed at all or not closed inside a finally block. This may be the cause of the problem on PostgreSQL. Ronald Wildenberg. -----------------------Disclaimer------------------------- Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor mogelijke onjuistheid en/of onvolledigheid van de hierin verstrekte informatie kan Kennisnet geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud van dit bericht (met bijlagen) rechten worden ontleend. De inhoud van dit bericht (met bijlagen) kan vertrouwelijke informatie bevatten en is uitsluitend bestemd voor de geadresseerde van dit bericht. Indien u niet de beoogde ontvanger van dit bericht bent, verzoekt Kennisnet u dit bericht te verwijderen, eventuele bijlagen niet te openen en wijst Kennisnet u op de onrechtmatigheid van het gebruiken, kopi�ren of verspreiden van de inhoud van dit bericht (met bijlagen). This message (with attachments) is given in good faith. Kennisnet cannot assume any responsibility for the accuracy or reliability of the information contained in this message (with attachments), nor shall the information be construed as constituting any obligation on the part of Kennisnet. The information contained in this message (with attachments) may be confidential or privileged and is only intended for the use of the named addressee. If you are not the intended recipient, you are requested by Kennisnet to delete this message (with attachments) without opening it and you are notified by Kennisnet that any disclosure, copying or distribution of the information contained in this message (with attachments) is strictly prohibited and unlawful. ----------------------------------------------------------
