db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-210) Network Server will leak prepared statements if not explicitly closed by the user until the connection is closed
Date Mon, 11 Apr 2005 01:11:27 GMT
Network Server will leak prepared statements if not explicitly closed by the user until the
connection is closed
----------------------------------------------------------------------------------------------------------------

         Key: DERBY-210
         URL: http://issues.apache.org/jira/browse/DERBY-210
     Project: Derby
        Type: Bug
  Components: Network Server  
    Reporter: Kathey Marsden


Network server will not garbage collect prepared statements that are not explicitly closed
by the user.  So  a loop like this will leak.

...
PreparedStatement ps;

 for (int i = 0 ; i  < numPs; i++)
	{

	 ps = conn.prepareStatement(selTabSql);
	 rs =ps.executeQuery();

	 while (rs.next())
	{
	    rs.getString(1);
	}
	rs.close();
	// I'm a sloppy java programmer
	//ps.close();

	}
			
To reproduce run the attached program 
java derbyStress

Both client and server will grow until the connection is closed.

 
It is likely that the fix for this will have to be in the client.  The client does not send
protocol to close the prepared statement, but rather reuses the PKGNAMCSN on the PRPSQLSTT
request once the prepared statement has been closed. This is how the server knows to close
the old statement and create a new one.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message