[DERBY-1166] Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: JDBC
• Assignee: Unassigned
• Reporter: David Van Couvering
• Created: 30/Mar/06 06:14
• Updated: 16/Jun/08 12:10
• Resolved: 30/Jul/07 20:11

Description

Currently in EmbedConnection.close(), if there is an active transaction a SQLException is thrown with SQLState.LANG_INVALID_TRANSACTION_STATE, or "25000". But looking at the SQL 2003 specification, the correct SQL State should be "25001" - "Active SQL-Transaction" (see section 17.3 - disconnect statement, under General Rules: "If any SQL-connection in L is active, then an exception condition is raised: invalid transaction state ?
active SQL-transaction.")

Although the stability classification for SQL States is currently under debate, for now we must assume that, although incorrect, this SQL State cannot be changed until the next major release.

Issue Links

• is duplicated by: DERBY-2065 Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.