[ http://issues.apache.org/jira/browse/DERBY-1732?page=comments#action_12438464 ] Daniel John Debrunner commented on DERBY-1732: ----------------------------------------------
Patch looks good, I don't think there needs to be a test here. If the code had been correct in the first place there would never have been a test case because it is not functionality that is being developed. > 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.5, 10.1.2.1, > 10.1.3.0, 10.3.0.0, 10.1.3.1, 10.2.2.0 > Reporter: Daniel John Debrunner > Assigned To: Sunitha Kambhampati > Fix For: 10.3.0.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
