[ https://jira.jboss.org/jira/browse/ISPN-220?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic updated ISPN-220: ------------------------------------- Attachment: infinispan_leak.zip Shows path to GC root of an object that is not garbage collected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-220?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic updated ISPN-220: ------------------------------------- Description: TestNG, during an execution of a test suite, keeps references to all executed test class instances. Our test classes, in some cases, keep references to instantiated caches, cache managers, and other heavy weight objects thus preventing those references from ever being garbage collected. Our test classes should *never* keep references to heavyweight objects other than in a test method scope. If we must keep reference to a cache or a cache manager in a class scope these references should be cleared and nulled in a method annotated with @AfterClass. Since TestNG does not traverse class hierarchy for invocation of @AfterClass annotated methods we have to ensure that every @AfterClass method is invoked in test class hierarchy (i.e call super). was: TestNG during an execution of a test suite keeps references to all executed test class instances. Our test classes in some cases keep references to instantiated caches thus preventing cache instances from ever being garbage collected. Our test classes should never keep references to cache instances other than in a test method scope. If truly there is a need to keep reference to a cache in a class scope these references should be cleared and nulled in a method annotated with @AfterClass. Of course, the same applies to any objects in class scope (cache managers etc etc.) Since TestNG does not traverse class hierarchy for invocation of @AfterClass annotated methods a special care has to be taken that every @AfterClass method is invoked in test class hierarchy (i.e call super). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-220?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic resolved ISPN-220. -------------------------------------- Resolution: Done Resolved. Introduced AbstractInfinispanTest as a superclass of all test classes. For more details see fisheye tab. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-220?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on ISPN-220: ------------------------------------------ As long as test class inherits from AbstractInfinispanTest all test class fields references will be nulled. However, if possible, a practice of not using test class fields should be employed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira