Derby
  1. Derby
  2. DERBY-1169

EmbedXAConnection.getConnection uses wrong SQL State when trying to close a connection with an active transaction

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1.2.1
    • Fix Version/s: None
    • Component/s: JDBC
    • Urgency:
      Low

      Description

      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.

        Activity

        Gavin made changes -
        Workflow jira [ 12352631 ] Default workflow, editable Closed status [ 12796886 ]
        Kathey Marsden made changes -
        Affects Version/s 10.1.2.1 [ 12310615 ]
        Rick Hillegas made changes -
        Urgency Low
        Rick Hillegas made changes -
        Labels derby_triage10_8
        Mike Matrigali made changes -
        Field Original Value New Value
        Component/s JDBC [ 11407 ]
        David Van Couvering created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            David Van Couvering
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development