JDO
  1. JDO
  2. JDO-372

ConcurrentPersistenceManagersSameClasses - Failed on second run

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: JDO 2 rc1
    • Fix Version/s: JDO 2 final (2.0)
    • Component/s: tck
    • Labels:
      None

      Description

      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.

      1. JDO-372.patch
        1 kB
        Craig L Russell
      2. JDO-372.patch
        0.7 kB
        Craig L Russell
      3. JDO-372-mbo.patch
        2 kB
        Michael Bouschen

        Activity

          People

          • Assignee:
            Michael Bouschen
            Reporter:
            Ilan Kirsh
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development