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
