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

Unload old JDBC drivers when done with them in the upgrade tests

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.9.1.0
    • Component/s: Test
    • Labels:
      None

      Description

      Discussed in this thread on derby-dev: http://mail-archives.apache.org/mod_mbox/db-derby-dev/201107.mbox/%3C4E146309.3000906@gmail.com%3E

      After we're done testing an old version in the upgrade tests, its classes are still loaded in the JVM because the old driver is referenced in DriverManager. We should find a way to unload the old drivers so that the memory usage of the upgrade tests is reduced. Now we typically need to run with -XX:MaxPermSize=200M or similar options to work around this issue.

        Attachments

        1. deregister.diff
          11 kB
          Knut Anders Hatlen
        2. deregister-v2.diff
          8 kB
          Knut Anders Hatlen
        3. clear-threadlocal.diff
          3 kB
          Knut Anders Hatlen
        4. deregister-check.diff
          5 kB
          Knut Anders Hatlen
        5. clear-contextservice.diff
          4 kB
          Knut Anders Hatlen

          Issue Links

            Activity

              People

              • Assignee:
                knutanders Knut Anders Hatlen
                Reporter:
                knutanders Knut Anders Hatlen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: