[
https://issues.apache.org/jira/browse/DERBY-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-1169:
---------------------------------
Labels: derby_triage10_8 (was: )
> EmbedXAConnection.getConnection uses wrong SQL State when trying to close a
> connection with an active transaction
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1169
> URL: https://issues.apache.org/jira/browse/DERBY-1169
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: David Van Couvering
> Labels: derby_triage10_8
>
> org.apache.derby.jdbc.EmbedXAConnection.close() should use SQLState 25001 -
> Invalid transaction state - active SQL-Transaction, when an attempt to close
> is made with an open global transaction. From the specification of disconnect
> in SQL 2003: 'If any SQL-connection in L is active, then an exception
> condition is raised: invalid transaction state ? active SQL-transaction."
> Currently it is using "XJ059", a Derby-specific SQL State.
> Although this is currently under debate, at this point we need to assume that
> SQL States can not change except across major release boundaries, so I am
> logging this bug but we can't fix it until 11.0.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
