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

[GSS](7.4.z) WFLY-20311 - Non-distributable SFSBs that are created but never invoked will never expire

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 7.4.24.GA
    • 7.4.20.GA
    • EJB
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      1. Use the included standalone.xml and ejb-in-war.war deployment from JBEAP-29013reproducer.zipo
      2. Run the indicated command from its README to create a potential EJB leak. The config uses a default timeout of 1 second so it should be cleaned up in that time. So once fixed, the below jmap histogram check should show a SimpleCache$Entry on the first check and then no value on the second. While broken, it will show the SimpleCache$Entry persists after timeout across both histogram checks.

      Show
      1. Use the included standalone.xml and ejb-in-war.war deployment from JBEAP-29013 reproducer.zipo 2. Run the indicated command from its README to create a potential EJB leak. The config uses a default timeout of 1 second so it should be cleaned up in that time. So once fixed, the below jmap histogram check should show a SimpleCache$Entry on the first check and then no value on the second. While broken, it will show the SimpleCache$Entry persists after timeout across both histogram checks.

      A non-distributed @Stateful Jakarta Enterprise Bean that defines a @StatefulTimeout schedules itself for expiration upon completion of the first method invocation. However, if such a SFSB is created, but never invoked, it will never expire.

        1. JBEAP-29013reproducer.zip
          433 kB

              rhn-support-aogburn Aaron Ogburn
              rhn-support-aogburn Aaron Ogburn
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: