[jboss-jira] [JBoss JIRA] Created: (JBAS-4420) Separate classloader leak tests from the 'all' tests

[Brian Stansberry (JIRA)]

Separate classloader leak tests from the 'all' tests
----------------------------------------------------

                 Key: JBAS-4420
                 URL: http://jira.jboss.com/jira/browse/JBAS-4420
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Test Suite
    Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.1.CR1


The classloader leak unit tests may generate enough garbage to fill 99.9% of free memory if there is a leak or if some SoftReference prevents collection of the classloader for a while. The memory is released as part of the test (which includes System.gc() calls in finally blocks to make sure the gc runs to clean it up before the next test.)  Still, filling the heap like that is potentially disruptive to the VM, so these tests should be separated into their own test run, segregated from the main 'all' tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira