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

SFSB expiration failures cause memory leak

XMLWordPrintable

    • Hide

      Configure attached Byteman script that triggers the bug.

      Attached reproducer contains a simple EJB and a jsp (http://localhost:8080/test to run) that calls the EJB to trigger the bug, waits to give expiration a chance to run, then tries to call the EJB again. The JSP logs "PASS" or "FAIL" to stdout.

      Note: SFSB in reproducer has a 1 minute timeout in order to trigger the bug somewhat quickly, and the byteman script waits accordingly. The wait would need to be increased for a longer SFSB timeout.

      Show
      Configure attached Byteman script that triggers the bug. Attached reproducer contains a simple EJB and a jsp ( http://localhost:8080/test to run) that calls the EJB to trigger the bug, waits to give expiration a chance to run, then tries to call the EJB again. The JSP logs "PASS" or "FAIL" to stdout. Note: SFSB in reproducer has a 1 minute timeout in order to trigger the bug somewhat quickly, and the byteman script waits accordingly. The wait would need to be increased for a longer SFSB timeout.
    • Release Notes

      There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely.

        1. test.ear
          4 kB
        2. WFLY-11897.btm
          0.3 kB

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

                Created:
                Updated:
                Resolved: