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

Derby

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

Created: 19/Aug/06 06:55 PM Updated: 14/Dec/06 01:31 AM

Component/s:

SQL, Store

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

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
derby1732.diff.txt	2006-09-28 02:53 PM	Sunitha Kambhampati	3 kB
derby1732.stat.txt	2006-09-28 02:53 PM	Sunitha Kambhampati	0.2 kB

Resolution Date:

14/Dec/06 01:31 AM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.