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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2006/11/28 16:00:24 UTC
[jira] Updated: (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 ]
Rick Hillegas updated DERBY-1732:
---------------------------------
Fix Version/s: 10.2.2.0
Ported to 10.2 branch at subversion revision 480074.
> 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
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.1.2.1, 10.3.0.0, 10.1.3.1, 10.2.2.0
> Reporter: Daniel John Debrunner
> Assigned To: Rajesh Kartha
> Fix For: 10.3.0.0, 10.2.2.0
>
> Attachments: derby1732.diff.txt, derby1732.stat.txt
>
>
> 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