You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2008/03/24 19:39:24 UTC

[jira] Created: (OPENJPA-543) Unclosed prepared statements in SQLStoreQuery.executeUpdate.

Unclosed prepared statements in SQLStoreQuery.executeUpdate.
------------------------------------------------------------

                 Key: OPENJPA-543
                 URL: https://issues.apache.org/jira/browse/OPENJPA-543
             Project: OpenJPA
          Issue Type: Bug
    Affects Versions: 1.0.2, 1.0.1, 1.0.0
            Reporter: Michael Dick
            Assignee: Michael Dick
             Fix For: 1.0.3, 1.1.0


SQLStoreQuery.executeUpdate only closes its prepared statements if an exception occurs. We should close the prepared statements immediately since they will tie up database resources (ie Oracle cursors). 

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


[jira] Closed: (OPENJPA-543) Unclosed prepared statements in SQLStoreQuery.executeUpdate.

Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENJPA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick closed OPENJPA-543.
--------------------------------

    Resolution: Fixed

> Unclosed prepared statements in SQLStoreQuery.executeUpdate.
> ------------------------------------------------------------
>
>                 Key: OPENJPA-543
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-543
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.3, 1.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> SQLStoreQuery.executeUpdate only closes its prepared statements if an exception occurs. We should close the prepared statements immediately since they will tie up database resources (ie Oracle cursors). 

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