JDK-4281444 : Bad syncronization code in bridge causes Function Sequence Error
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.
Calling stmt.close can cause function sequence errors in applications. This problem was introduced in jdk1.2.2 when syncronization was removed.
BugTraq+ Release Management Values
COMMIT TO FIX:
Calling Statement.close() closes any result sets associated with the statement. A race condition exists such that it is possible for the SQL_CLOSE to be called on a hStmt that has already SQL_DROP'ed.
This race condition does not occur readily in kestrel build L.