| Michael Bouschen (JIRA) 2006-04-24, 7:58 am |
| [ http://issues.apache.org/jira/browse/JDO-372?page=all ]
Michael Bouschen resolved JDO-372:
----------------------------------
Fix Version: JDO 2 final
Resolution: Fixed
Checked in the patch in the 2.0 branch and the trunk (see revision 396521).
> ConcurrentPersistenceManagersSameClasses
- Failed on second run
> ---------------------------------------------------------------
>
> Key: JDO-372
> URL: http://issues.apache.org/jira/browse/JDO-372
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Ilan Kirsh
> Assignee: Michael Bouschen
> Fix For: JDO 2 final
> Attachments: JDO-372-mbo.patch, JDO-372.patch, JDO-372.patch
>
> 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 fai
l on any additional run on the same database files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|