Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5870

Memory leak when doing deploy/undeploy app using REST and JPA

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR8
    • None
    • REST, XML Frameworks
    • None
    • Regression
    • Hide
      1. decrease metaspace in EAP - e.g. -XX:MetaspaceSize=1M -XX:MaxMetaspaceSize=100m
      2. build and deploy attached app
      3. get http://localhost:8080/memoryLeak/webresources/user
      4. undeploy
      5. repeat from step 2 until OOM occurs
      Show
      decrease metaspace in EAP - e.g. -XX:MetaspaceSize=1M -XX:MaxMetaspaceSize=100m build and deploy attached app get http://localhost:8080/memoryLeak/webresources/user undeploy repeat from step 2 until OOM occurs

    Description

      It seems that exposing some type (ApplicationUser in attached app) which has enum type as attribute via REST api could cause memory leak (See steps to reproduce). You can observe that person.joey.test.UserType instances are kept in memory when GC happens (metaspace exceeds) and the path to GC root looks:

      Note that this map https://github.com/FasterXML/jackson-databind/blob/jackson-databind-2.7.4/src/main/java/com/fasterxml/jackson/databind/util/ClassUtil.java#L366 was not available in 2.5.4 version used in WF 10.0.0.Final

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. WFLY-7037 Memory leak when doing deploy/undeploy app using REST and JPA

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-5854 Memory leak when doing deploy/undeploy app using REST and JPA

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Component Upgrade - A task tracking an update to a bundled component JBEAP-6290 Upgrade jackson to version that has fix for JBEAP-5870

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JBEAP

              People

                sdouglas1@redhat.com Stuart Douglas
                tremes1@redhat.com Tomas Remes
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: