Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-173

org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase (testTimestampStrategyFail) alternately passes and fails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.RC5
    • 4.2.RC2
    • System
    • None
    • I am seeing this behaviour on all Windows environments (x86-Sun JVM, x86_64-Sun JVM, x86-BEA, x86_64-BEA)

    • Medium

      This test involves a FacadeBean (containing test methods) and a CMP entity bean (string two sets of values string1, integer1, double1, string2, integer2, double2).
      The aim of the test seems to be to set up a concurrent access between a single CMP entity bean and two instances of the Facade bean (which manipulate the CMP Beans state), and check that an exeption is raised (i.e. access by the second instance of the Facade bean should fail).

      This test alternately passes and fails when run on the same architecture-OS-JVM combination within the target tests-unified.

      The tests-unified target runs the test against two configurations: unified-jboss and unified-java.
      The test alternately passes and fails against both of these configurations.

      Thus, there is some non-determinism within this test which should be resolved.

      I have attached the relevant output (client-side TESTS-*.xml file, and server side output.log and server.log) for a test case failure on the configuration unified jboss.

              rachmato@redhat.com Richard Achmatowicz
              rachmato@redhat.com Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: