db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samuel Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-255) Closing a resultset after retrieving a large > 32K value with Network Server does not release locks
Date Thu, 02 Jun 2005 20:18:56 GMT
     [ http://issues.apache.org/jira/browse/DERBY-255?page=all ]

Samuel Andrew McIntyre updated DERBY-255:
-----------------------------------------

        Version: 10.0.2.1
                 10.0.2.0
                 10.0.2.2
                 10.1.0.0
    Fix Version: 10.1.0.0
                     (was: 10.0.2.1)

> 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
>     Versions: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.0.0
>     Reporter: Kathey Marsden
>     Assignee: Kathey Marsden
>      Fix For: 10.1.0.0
>  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


Mime
View raw message