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

[GSS](7.2.z) Memory leak in FlashScope - expired elements are not cleared

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.2.5.CR1, 7.2.5.GA
    • 7.2.3.GA
    • JSF
    • None
    • +
    • Hide
      • Using SessionScope instead of FlashScope for POST-REDIRECT-GET.
      • Set com.sun.faces.numberOfConcerrentFlashUsers and com.sun.faces.numberOfFlashesBetweenFlashReapings to web.xml as following 
        <context-param>
    <param-name>com.sun.faces.numberOfConcerrentFlashUsers</param-name>
    <param-value>10</param-value>
</context-param>
<context-param>
    <param-name>com.sun.faces.numberOfFlashesBetweenFlashReapings</param-name>
    <param-value>1</param-value>
</context-param>
      Show
      Using SessionScope instead of FlashScope for POST-REDIRECT-GET. Set com.sun.faces.numberOfConcerrentFlashUsers and com.sun.faces.numberOfFlashesBetweenFlashReapings to web.xml as following <context-param> <param-name> com.sun.faces.numberOfConcerrentFlashUsers </param-name> <param-value> 10 </param-value> </context-param> <context-param> <param-name> com.sun.faces.numberOfFlashesBetweenFlashReapings </param-name> <param-value> 1 </param-value> </context-param>
    • Hide

      1. Deploy the attached reproducer.
      2. Press "Accumulate 100MB in FlashScope" button several times, then, OOMError will occur.

      Show
      1. Deploy the attached reproducer. 2. Press "Accumulate 100MB in FlashScope" button several times, then, OOMError will occur.

    Description

      Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed.

      If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon.

      @Model
public class Action {

    private static final int oneHundredMB = 1024 * 1024 * 100;

    public String next() {
        Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash();
        flash.putNow("huge", new byte[oneHundredMB]);
        return "index.xhtml?faces-redirect=true";
    }
}

      When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated.

      Class Name                                                             | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap
-----------------------------------------------------------------------------------------------------------------------------------------
java.lang.Thread @ 0xeea24380  default task-1 Thread                   |            1 |          120 |                64 |        20,800
'- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608       |            1 |           40 |                64 |            64
   '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630|            1 |           64 |                64 |   314,574,048
-----------------------------------------------------------------------------------------------------------------------------------------

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12643 Memory leak in FlashScope - expired elements are not cleared

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19407 [GSS](7.3.z) Memory leak in FlashScope - expired elements are not cleared

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17739 [GSS](7.1.z) Memory leak in FlashScope - expired elements are not cleared

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17582 [GSS](7.2.z) Upgrade JSF based on Mojarra 2.3.5.SP3-redhat-00002 to 2.3.5.SP3-redhat-00003

          • 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.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17856 [GSS](7.2.z) Flash Scope is not cleared when JSF1095 is occurred

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17743 (7.3.z) Upgrade JSF based on Mojarra 2.3.9.SP04

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          links to

          Web Link Mojarra issue 4631

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              rhn-support-nagetsum Norito Agetsuma
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: