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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.2.2.0, 10.3.1.4
• Component/s: SQL, Store
• Assignee: Sunitha Kambhampati
• Reporter: Daniel John Debrunner
• Created: 19/Aug/06 18:55
• Updated: 14/Dec/06 01:31
• Resolved: 14/Dec/06 01:31

Description

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.