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

DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.3, 10.5.1.1
    • Fix Version/s: 10.5.1.1
    • Component/s: JDBC, Network Client
    • Labels:
      None
    • Environment:
      Client-server with connection pooling enabled.

      Description

      The connection returned from DatabaseMetaData.getConnection is not the same as the connection used to create the meta data object when the client driver is used with connection pooling enabled.
      For trunk, the embedded driver/ds does the right thing.

        Attachments

        1. derby-3431-1a-test_repro.diff
          2 kB
          Kristian Waagan
        2. derby-3431-1b-test_repro.diff
          2 kB
          Kristian Waagan
        3. derby-3431-2a-test.diff
          2 kB
          Kristian Waagan
        4. derby-3431-3a-client_logical_metadata.diff
          43 kB
          Kristian Waagan
        5. derby-3431-3a-client_logical_metadata.stat
          0.5 kB
          Kristian Waagan
        6. derby-3431-3b-client_logical_metadata.diff
          44 kB
          Kristian Waagan
        7. derby-3431-4a-spt_test_nit.diff
          0.7 kB
          Kristian Waagan

          Issue Links

            Activity

              People

              • Assignee:
                kristwaa Kristian Waagan
                Reporter:
                kristwaa Kristian Waagan
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: