[ http://issues.apache.org/jira/browse/DERBY-255?page=comments#action_66527 ] Kathey Marsden commented on DERBY-255: --------------------------------------
Checked this in with revision 179014. Sending java\drda\org\apache\derby\impl\drda\DDMWriter.java Sending java\drda\org\apache\derby\impl\drda\DRDAConnThread.java Adding java\drda\org\apache\derby\impl\drda\EXTDTAInputStream.java Sending java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\blobclob4BLOB.out Sending java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\blobclob4BLOB.out Sending java\testing\org\apache\derbyTesting\functionTests\master\blobclob4BLOB.out Sending java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\blobclob4BLOB.java Transmitting file data ....... Committed revision 179014. > Closing a resultset after retrieving a large > 32K value with Network Server > does not release locks > --------------------------------------------------------------------------------------------------- > > Key: DERBY-255 > URL: http://issues.apache.org/jira/browse/DERBY-255 > Project: Derby > Type: Bug > Reporter: Kathey Marsden > Assignee: Kathey Marsden > Attachments: LargeDataLocks.java, derby255.diff > > Closing a resultset after retriving BLOB or CLOB data > 32K, does not release > locks properly. Network Server uses getClob, getBlob to retrieve the data > even if the application uses getCharacteStream, etc, so holds locks to the > end of the transaction. > To reproduce run attached repro > java LargeDataLocks derbynetclient > > To see the difference with embedded > java LargeDataLocks derby -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
