db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1169) EmbedXAConnection.getConnection uses wrong SQL State when trying to close a connection with an active transaction
Date Tue, 11 Apr 2006 23:15:26 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1169?page=all ]

Mike Matrigali updated DERBY-1169:
----------------------------------

    Component: JDBC

> EmbedXAConnection.getConnection uses wrong SQL State when trying to close a connection
with an active transaction
> -----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1169
>          URL: http://issues.apache.org/jira/browse/DERBY-1169
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Reporter: David Van Couvering

>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message