Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ResultSet.close() never sends Xclose to free resources #3786

monetdb-team opened this issue Nov 30, 2020 · 0 comments

ResultSet.close() never sends Xclose to free resources #3786

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2015-08-12 13:28:45 +0200
From: @hannesmuehleisen
To: clients devs <>
Version: 11.19.9 (Oct2014-SP2)

Last updated: 2015-08-28 13:42:37 +0200

Comment 21124

Date: 2015-08-12 13:28:45 +0200
From: @hannesmuehleisen

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:

The JDBC driver never tells the server to free result sets. This leads to result sets piling up for long-running connections and a steady growth of the dbfarm.

Reproducible: Always

Steps to Reproduce:

  1. Open a JDBC connection
  2. Run many SELECT queries with large result sets on this connection
  3. Actually call close() on result sets

Actual Results:

dbfarm grows until the disk is full

Expected Results:

No permanent increase in size

Comment 21125

Date: 2015-08-12 13:32:21 +0200
From: MonetDB Mercurial Repository <>

Changeset bbd59fc85a93 made by Hannes Muehleisen in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bbd59fc85a93

Changeset description:

JDBC Driver: Send Xclose <queryid> on ResultSet.close() if required
This fixes Bug #3786

Comment 21214

Date: 2015-08-28 13:42:37 +0200
From: @sjoerdmullender

Jul2015 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant