Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1004

Client should not require user to rollback the active transaction before call to PooledConnection.getConnection()

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.1.3.1, 10.2.1.6
    • Fix Version/s: 10.1.3.1, 10.2.1.6
    • Component/s: Network Client
    • Labels:
      None

      Description

      For a PooledConnection.getConnection() the connection gets closed.
      Embedded automatically rolls back any activity on the connection.
      Client requires the user to rollback and gives an SQLException
      java.sql.Connection.close() requested while a transaction is in progress

      The test jdbcapi/checkDataSource.java shows this bug. A boolean needRoolbackBeforePCGetConnection has been added to the test and explicit rollback has been added to the test to get it to run with client.

      To reproduce take out instances of the explicit rollback for client from the test e.g.

      if (needRollbackBeforePCGetConnection)
      c1.rollback();

        Attachments

        1. DERBY-1004.diff
          5 kB
          David Van Couvering

          Activity

            People

            • Assignee:
              davidvc David Van Couvering
              Reporter:
              kmarsden Katherine Marsden
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: