You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2005/05/25 00:57:52 UTC

[jira] Assigned: (DERBY-255) Closing a resultset after retrieving a large > 32K value with Network Server does not release locks

     [ http://issues.apache.org/jira/browse/DERBY-255?page=all ]

Kathey Marsden reassigned DERBY-255:
------------------------------------

    Assign To: Kathey Marsden

> 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
>
> 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