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 "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/09/26 20:05:53 UTC

[jira] Assigned: (DERBY-1732) The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors

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

Sunitha Kambhampati reassigned DERBY-1732:
------------------------------------------

    Assignee: Sunitha Kambhampati

> The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1732
>                 URL: http://issues.apache.org/jira/browse/DERBY-1732
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL, Store
>            Reporter: Daniel John Debrunner
>         Assigned To: Sunitha Kambhampati
>
> Don't have the exact details, but remember noticing it a while ago. I think the store transaction context closes the transaction on such an error, while the language conneciton context just rollsback the transaction or the statement. I think the best and consistent approach would be to close the connection.

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