Uploaded image for project: 'mod-circulation'
  1. mod-circulation
  2. CIRC-969

Event publishing causes memory leak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: P1
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 19.2.1, 20.0.0
    • Labels:
      None
    • Template:
      Standard Bug Write-Up Format
    • Sprint:
      EPAM-Veg Sprint 100, EPAM-Veg Sprint 101
    • Story Points:
      1
    • Development Team:
      Vega
    • Release:
      Q3 2020 Bug Fix
    • Confidence factor:
      Medium

      Description

      Overview:
      As Taras Spashchenko stated in CIRC-961 comments, "the usage of PubSubClientUtils outside of the Vert.x context in mod-circulation that causes the creation of new Vert.x instances again and again", which causes memory leak.

      Possible solution: use thenCompose and thenApply methods instead of thenComposeAsync and thenApplyAsync for sending event messages.

      Steps to Reproduce:

      1. Trigger events that cause sending of event messages
      2. Check module's memory for VertxImpl objects

      Expected Results:
      The number of VertxImpl objects is not increasing
      Actual Results:
      The number of VertxImpl objects increases after every event

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                oleksandrkurash Alexander Kurash
                Reporter:
                oleksandrkurash Alexander Kurash
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases