db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1732) The langauge and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors
Date Sat, 19 Aug 2006 18:57:13 GMT
The langauge 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


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

        

Mime
View raw message