java.lang.OutOfMemory running TCK with validateTables false

• Key: JDO-21
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Michelle Caisse
• Reporter: Michelle Caisse
• Component/s: tck2
• Fix Version/s: JDO 2 beta

Description

When org.jpox.validateTables=false (default is true), numerous java.lang.OutOfMemory exceptions are thrown. The TCK needs to run with this option false, so this is a problem. My box has plenty of available memory when this occurs. The problem does not occur when running any individual test. This is probably a JPOX problem, but I enter it here pending further investigation.

Comments

[Michelle Caisse]

Checked in temporary work-around for this problem (r 164936) -- increased maximum heap size to 512MB. Clearly there is a resource leak because memory usage increases with time as TCK tests are run.

[Michelle Caisse]

Checked to see if pmf is closed. In general it is. However, with 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.

Also certain tests use big chunks for memory that is not subsequently recovered -- some of the fieldtypes tests (~200MB as a group) and one of these: NewQueryWithExtentAndFilter or NewQueryWithSpecifiedLanguageAndQuery (~200MB). I could not reproduce this when running the individual tests; I observed it while running the whole TCK. The pmf is closed for these tests, so something else is using the memory.

[Michelle Caisse]

Problem no longer occurs.

[Michael Bouschen]

Reopened to set the Fix Version/s field to JDO 2 beta.