
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Jan/08 07:43 PM
|
|
In a Java procedure called from SQL any dynamic ResultSets that are created using a PreparedStatement or CallableStatement leave their activations open until :
- the statement that created it is garbage collected (which requires the outer statement to be garbage collected)
- and the LCC processes unused Activations.
Dynamic ResultSets that are created by a Statement object are handled correctly because they are marked single use activation and thus the close of the ResultSet also closes the activation.
Fix is to mark the activation as single use in EmbedResultSet when the EmbedResultSet is marked as being a dynamic ResultSet. This will then lead to the close of the ResultSet also closing the activation.
Can't see how to write a test for this, I can see the activations stacking up in a debugger, but typically there will be no visible user impact.
|
|
Description
|
In a Java procedure called from SQL any dynamic ResultSets that are created using a PreparedStatement or CallableStatement leave their activations open until :
- the statement that created it is garbage collected (which requires the outer statement to be garbage collected)
- and the LCC processes unused Activations.
Dynamic ResultSets that are created by a Statement object are handled correctly because they are marked single use activation and thus the close of the ResultSet also closes the activation.
Fix is to mark the activation as single use in EmbedResultSet when the EmbedResultSet is marked as being a dynamic ResultSet. This will then lead to the close of the ResultSet also closing the activation.
Can't see how to write a test for this, I can see the activations stacking up in a debugger, but typically there will be no visible user impact. |
Show » |
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#610895 |
Thu Jan 10 19:41:20 UTC 2008 |
djd |
DERBY-3247 Mark the activations for dynamic result sets as single use once they are returned to the applications JDBC statement. Ensures that the close of the ResultSet will close the activation.
Merge of Revision 601386 from trunk excluding the changes to EmbedStatement. Those changes were comments to the finalizer method which does not exist in 10.3
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.3/java/engine/org/apache/derby/impl/jdbc/EmbedResultSet.java
|
|