db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2885) Wrong connection object used in EmbedConnection.clearLOBMapping()
Date Sat, 30 Jun 2007 17:23:04 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-2885:
--------------------------------------

    Attachment: lobmap.diff

The attached patch changes clearLOBMapping() so that it checks rootConnection.lobHashMap instead
of this.lobHashMap, and so that it only calls getlobHMObj().clear() if rootConnection.lobHashMap
is non-null. I have started the full regression test suite.

> Wrong connection object used in EmbedConnection.clearLOBMapping()
> -----------------------------------------------------------------
>
>                 Key: DERBY-2885
>                 URL: https://issues.apache.org/jira/browse/DERBY-2885
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Performance
>    Affects Versions: 10.3.1.0, 10.3.1.1, 10.4.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For: 10.3.1.1, 10.4.0.0
>
>         Attachments: lobmap.diff
>
>
> I think there are two bugs in EmbedConnection.clearLOBMapping():
>   1) It checks if lobHashMap is non-null, but it should have checked rootConnection.lobHashMap.
>   2) It calls getlobHMObj().clear() regardless of whether there is a HashMap. This creates
a HashMap object even though it's not needed, and all the subsequent transactions on that
connection have to perform cleanup on that object.

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


Mime
View raw message