Uploaded image for project: 'mod-patron-blocks'
  1. mod-patron-blocks
  2. MODPATBLK-43

Leaked HTTP Clients and Connection Mananger

    XMLWordPrintable

    Details

    • Template:
      Standard Bug Write-Up Format
    • Sprint:
      EPAM-Veg Sprint 98, EPAM-Veg Sprint 99
    • Story Points:
      2
    • Development Team:
      Vega
    • Release:
      Q3 2020

      Description

      Performance testing of check-in and check-out show that mod-patron-blocks creates and holds on to HTTP Clients. Attached is a heap-dump memory-leak-suspect report mod-patron-blocks_Leak_Leak_Suspects.zip generated by the Eclipse heap dump tool showing HttpClientImpl and ConnectionMananager objects being held in memory. This problem was found in the Goldenrod release.

      steps to reproduce
      Run the check-in-check-out performance test for over an hour. This test calls the following API which incurs the memory leaks: /automated-patron-blocks/

      {userID}

      . So, technically, calling this API over and over again in an hour would generate the leaks.

      Expected outcome
      No memory leaks over time

      Interested parties
      Holly Mistlebauer

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                OleksandrVidinieiev Oleksandr Vidinieiev
                Reporter:
                mtraneis Martin Tran
                Tester Assignee:
                Martin Tran Martin Tran
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases