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

"No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1
    • 10.3.3.0, 10.4.1.3, 10.5.1.1
    • Network Client
    • None

    Description

      This is the client version of bug DERBY-2142. It can be reproduced by enabling the test, DataSourceTest.testPooledReuseOnClose() for client. I am opening a new issue for client as the embedded fix was backported to 10.1 and I am guessing the client fix won't be backported that far. Better to keep it as a separate issue.

      Attachments

        1. derby-3379-1a-enforce_no_chaining.diff
          7 kB
          Kristian Waagan
        2. derby-3379-1a-enforce_no_chaining.diff
          7 kB
          Kristian Waagan
        3. derby-3379-1a-enforce_no_chaining.stat
          0.3 kB
          Kristian Waagan
        4. derby-3379-1a-enforce_no_chaining.stat
          0.3 kB
          Kristian Waagan
        5. derby-3379-1b-enforce_no_chaining.diff
          6 kB
          Kristian Waagan
        6. derby-3379-1c-enforce_no_chaining.diff
          6 kB
          Kristian Waagan
        7. derby-3379-1c-enforce_no_chaining.stat
          0.3 kB
          Kristian Waagan
        8. derby-3379-2a-comment_and_JavaDoc.diff
          3 kB
          Kristian Waagan
        9. derby-3379-3a-minimal_fix_and_test_enabling.diff
          3 kB
          Kristian Waagan

        Issue Links

          Activity

            People

              kristwaa Kristian Waagan
              kmarsden Katherine Marsden
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: