Derby
  1. Derby
  2. DERBY-4743

Attempt to access a DECLARE GLOBAL TEMPORARY TABLE after commit in an XA transaction in Network server fails.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
    • Fix Version/s: 10.7.1.1
    • Component/s: JDBC

      Description

      Attempting to access a global temporary table after commit of an XA transaction in network server fails. Does anyone know if this is
      actually meant to work. After a commit of an XA transaction in network server do the connection keep the same transaction context for
      subsequent work? I will commit a change to the XATest.java junit test that shows this. Is it valid to attempt to use the connection after an
      XA end() and XA commit()?

      1. XATest.java
        48 kB
        Mike Matrigali

        Issue Links

          Activity

            People

            • Assignee:
              Mike Matrigali
              Reporter:
              Mike Matrigali
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development