Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-6451

Investigate potential HortnetQ memory leak issues in UPS usage

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • EAP-6.4.4

    • IR294 - BF Openshift Jenkins, IR295 - eteam LastOf16
    • 5

      Using the Eclipse Memory Analyzer there are two potential leaks when running the UPS potentials

      • Problem Suspect 1
        One instance of "org.hornetq.core.paging.impl.PagingManagerImpl" loaded by "org.jboss.modules.ModuleClassLoader @ 0xb26cfd50" occupies 144,656,512 (38.17%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentHashMap$Segment[]" loaded by "<system class loader>".
         
        Keywords
        org.hornetq.core.paging.impl.PagingManagerImpl
        org.jboss.modules.ModuleClassLoader @ 0xb26cfd50
        java.util.concurrent.ConcurrentHashMap$Segment[]
        
      • Problem Suspect 2
        One instance of "org.hornetq.core.journal.impl.JournalImpl" loaded by "org.jboss.modules.ModuleClassLoader @ 0xb26cfd50" occupies 91,759,128 (24.21%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentHashMap$Segment[]" loaded by "<system class loader>".
         
        Keywords
        org.hornetq.core.journal.impl.JournalImpl
        org.jboss.modules.ModuleClassLoader @ 0xb26cfd50
        java.util.concurrent.ConcurrentHashMap$Segment[]
        

        1. data.zip
          19.86 MB
        2. Memory_issues.png
          Memory_issues.png
          170 kB

            Unassigned Unassigned
            mwessend@redhat.com Matthias Wessendorf
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: