Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1442

Ejb3ClassloaderLeakUnitTestCase failures in AS testsuite

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 1.0.0-Beta2
    • None
    • None
    • None

    Description

      The Ejb3ClassloaderLeakUnitTestCase tests started failing on Jul 17 (see https://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/746/). I ran the test with the JBoss Profiler analysis of the classloader leak enabled and found that a proxy remains bound in JNDI after bean undeploy, leaking the CL. I will attach the classloader leak report.

      Attachments

        1. ClassLoader.html
          0.5 kB
        2. Proxy.html
          439 kB

        Issue Links

          duplicates

          Sub-task - The sub-task of the issue JBAS-5252 Fix classloader leak test failures

          • 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.
          • Closed
          is blocked by

          Sub-task - The sub-task of the issue EJBTHREE-1385 Refactor SessionSpecContainers to use new Proxy component

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1473 Remote ProxyFactories not unregistered from AOP Dispatcher

          • 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.
          • Resolved

          Activity

            People

              arubinge@redhat.com Andrew Rubinger (Inactive)
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: