Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
1.0.6
-
EPAM-Veg Sprint 98, EPAM-Veg Sprint 99
-
2
-
Vega
-
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/
. 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
- is cloned by
-
MODORG-42 Replace old HTTP Clients with Vertx WebClient
-
- Closed
-
- relates to
-
MODFEE-93 Leaked HTTP Clients and Connection Mananger
-
- Closed
-
-
MODFEE-101 SPIKE - Investigate memory leak issues
-
- Closed
-