Fatal error upon executeUpdate() on closed databases

What steps will reproduce the problem?
1. close db
2. do Statement.executeUpdate() on the connection

What is the expected output? What do you see instead?

Please provide any additional information below.

I receive the fatal error below when I attempt a call to 
Statement.executeUpdate() on a closed database.  Neither a SQLException, 
nor a generic Exception catch the error.   The Xentus driver appears to 
catch the same error without a fatal crash.

As a workaround, before executing any SQL statement, I first check 
Connection.isClosed() and throw a custom exception if the database is 
closed. 

I'm using sqlite-jdbc-3.6.19.jar with Java 6.0_16.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6b0fca80, pid=5076, 
tid=2156
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode windows-x86 )
# Problematic frame:
# C  [sqlite-3.6.19-sqlitejdbc.dll+0x3ca80]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  S Y S T E M  ---------------

OS: Windows XP Build 2600 Service Pack 3

CPU:total 1 (1 cores per cpu, 2 threads per core) family 15 model 4 
stepping 10, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht

Memory: 4k page, physical 2097151k(2097151k free), swap 4194303k(3951816k 
free)

vm_info: Java HotSpot(TM) Client VM (14.2-b01) for windows-x86 JRE 
(1.6.0_16-b01), built on Jul 31 2009 11:26:58 by "java_re" with MS VC++ 7.1

time: Fri Dec 04 03:00:26 2009
elapsed time: 74 seconds

Original issue reported on code.google.com by taroleo on 4 Dec 2009 at 9:41

RawrUniversal / xerial

Fatal error upon executeUpdate() on closed databases #52