[#JDO-372] ConcurrentPersistenceManagersSameClasses - Failed on second run

JDO

ConcurrentPersistenceManagersSameClasses - Failed on second run

Created: 23/Apr/06 12:34 AM Updated: 24/Apr/06 06:46 PM

Return to search

Component/s:

tck2

Affects Version/s:

JDO 2 rc1

Fix Version/s:

JDO 2 final

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
JDO-372-mbo.patch	2006-04-24 12:16 AM	Michael Bouschen	2 kB
JDO-372.patch	2006-04-23 09:54 PM	Craig Russell	1 kB
JDO-372.patch	2006-04-23 09:40 PM	Craig Russell	0.7 kB

Resolution Date:

24/Apr/06 06:46 PM

Description

« Hide

Thanks to deleteTearDownClasses / deleteTearDownInstances, most test cases can run on either a clean database or on an existing database. Unfortunately, it seems that org.apache.jdo.tck.ConcurrentPersistenceManagersSameClasses is different. Old objects are not deleted from the 2nd database that this test case uses, so findPoint may return more than one result object, and the first result that is checked might be an old object from a previous run. Therefore, the test case passes the first run and may fail on any additional run on the same database files.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.