Derby
  1. Derby
  2. DERBY-341

Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

    Details

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

      Description

      If a logical connection has already been obtained, client should disallow XAConnection getConnection if a global transaction has been started and a logical connection has already been obtained

      Repro:

      With the client the script below does not give an error.

      ij> connect 'wombat;create=true';
      ij> disconnect;
      ij> xa_datasource 'wombat';
      ij> xa_connect user 'APP' password 'xxx';
      Connection number: 3.
      ij> – start new transaction
      xa_start xa_noflags 0;
      ij> xa_getconnection;
      ij> – Should not be able to get connection again
      xa_getconnection;

      With embedded we get.
      ERROR XJ059: Cannot close a connection while a global transaction is still active.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Kathey Marsden
          • Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development