JDK-4281444 : Bad syncronization code in bridge causes Function Sequence Error
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.sql:bridge
  • Affected Version: 1.2.2
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-10-15
  • Updated: 1999-10-25
  • Resolved: 1999-10-25
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.

To download the current JDK release, click here.
1.3.0 kestrelFixed
Calling stmt.close can cause function sequence errors in applications. This problem was introduced in jdk1.2.2 when syncronization was removed.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel FIXED IN: kestrel INTEGRATED IN: kestrel

EVALUATION jon.ellis@Eng 1999-10-14 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. jon.ellis@Eng 1999-10-25 This race condition does not occur readily in kestrel build L.