Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11970

SFSB memory leak due to Date() usage

    XMLWordPrintable

Details

    • Hide

      Access an SFSB.
      Change the system time backwards before the SFSB expiration time elapses (I ran "date", then copy/pasted it into "date -s" several seconds later).
      Wait sufficient time for expiration (and potential retry) and attempt to access bean again.

      Expected: bean no longer exists.
      Actual: bean never expires.

      Show
      Access an SFSB. Change the system time backwards before the SFSB expiration time elapses (I ran "date", then copy/pasted it into "date -s" several seconds later). Wait sufficient time for expiration (and potential retry) and attempt to access bean again. Expected: bean no longer exists. Actual: bean never expires.
    • Release Notes

    Description

      SFSB tracks expiration with "new Date().getTime()" and "System.currentTimeMillis()".
      But the expiration threads are scheduled (inside JDK classes) with System.nanoTime().

      If the expiration task runs before the bean is considered expired, the expiration check fails and the bean is never expired.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16703 [GSS](7.2.z) WFLY-11970 - SFSB memory leak due to Date() usage

          • 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

            People

              pferraro@redhat.com Paul Ferraro
              rhn-support-dereed Dennis Reed
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: