Issue Details (XML | Word | Printable)

Key: JDO-32
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Michael Bouschen
Reporter: Michelle Caisse
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JDO

Some tests, when they fail, do not close pmf

Created: 30/Apr/05 02:38 AM   Updated: 23/Apr/06 02:11 AM
Return to search
Component/s: tck2
Affects Version/s: None
Fix Version/s: JDO 2 beta

Time Tracking:
Not Specified

Resolution Date: 23/Apr/06 02:11 AM


 Description  « Hide
Classes in the api.persistencemanager package and subpackages, when the test FAILS, or in some cases when there is an ERROR, pmf is not closed. This is responsible for about 200MB of unrecovered memory usage, causing java.lang.OutOfMemoryError before a work-around was checked in. See JDO-21.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Michael Bouschen added a comment - 06/May/05 06:49 AM
I changed method closePMF in the tck test superclass JDO_Test. If method closing the PersistenceManagerFactory fails, it checkes for open PersistenceManagers, closes them and closes the PMF again. I did a similar change in the test superclass of the ri11 test cases.

Another change is in the superclass of the PersistenceManager test. It implements a cleanup method that is called before the PMF is closed. In the old implementation any cleanup failure bypasses the code that closes the pmf. I changed this such that the pmf is closed in any case.

Michael Bouschen added a comment - 23/Apr/06 02:08 AM
Reopened to set the Fix Version/s field to JDO 2 beta.