db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError
Date Tue, 12 Feb 2008 17:19:08 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568226#action_12568226

Kathey Marsden commented on DERBY-3354:

Also should the removeLobMapping calls be removed from LobStoredProcedures.BLOBRELEASELOCATOR
and CLOBRELEASELOCATOR now that the release happens in free()?

> Select from large lob table with embedded gives OutOfMemoryError
> ----------------------------------------------------------------
>                 Key: DERBY-3354
>                 URL: https://issues.apache.org/jira/browse/DERBY-3354
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,
>            Reporter: Kathey Marsden
>         Attachments: derby-3354.diff, LocLeak.java
> Retrieving from a large table with lobs gives an OutOfMemoryException, even if free()
is explictly called on the lob.   I believe this is because EmbedConnection.addLobMapping
is called for every lob creation but is never cleared until commit or rollback, even if the
lob is freed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message