Uploaded image for project: 'JBoss Cache'
  1. JBoss Cache
  2. JBCACHE-1

EvictionLocalStressTestCase consistently failing on MT system

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      Running this 3 times on a dual proc redhat system results in 2 failures:

      [starksm@lamia testsuite]$ run_tests.sh
      Buildfile: build.xml
      Overriding previous definition of reference to xdoclet.task.classpath

      one-test:
      [mkdir] Created dir: /cvs/JBoss4.0/jboss-4.0/testsuite/output/log
      [junit] Running org.jboss.test.cache.stress.EvictionLocalStressTestCase
      [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 55.674 sec
      [junit] Test org.jboss.test.cache.stress.EvictionLocalStressTestCase FAILED

      BUILD SUCCESSFUL
      Total time: 59 seconds
      [starksm@lamia testsuite]$ run_tests.sh
      Buildfile: build.xml
      Overriding previous definition of reference to xdoclet.task.classpath

      one-test:
      [mkdir] Created dir: /cvs/JBoss4.0/jboss-4.0/testsuite/output/log
      [junit] Running org.jboss.test.cache.stress.EvictionLocalStressTestCase
      [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 67.995 sec

      BUILD SUCCESSFUL
      Total time: 1 minute 12 seconds
      [starksm@lamia testsuite]$ run_tests.sh
      Buildfile: build.xml
      Overriding previous definition of reference to xdoclet.task.classpath

      one-test:
      [mkdir] Created dir: /cvs/JBoss4.0/jboss-4.0/testsuite/output/log
      [junit] Running org.jboss.test.cache.stress.EvictionLocalStressTestCase
      [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 55.566 sec
      [junit] Test org.jboss.test.cache.stress.EvictionLocalStressTestCase FAILED

      BUILD SUCCESSFUL
      Total time: 59 seconds

      The exception from the last run is:
      lock could not be acquired after 15000 ms. Lock map ownership Read lock owners: [<null>:52]
      Write lock owner: null
      ; - nested throwable: (org.jboss.cache.lock.TimeoutException: lock could not be acquired after 15000 ms. Lock map ownership Read lock owners: [<null>:52]
      Write lock owner: null
      )
      org.jboss.util.NestedRuntimeException: lock could not be acquired after 15000 ms. Lock map ownership Read lock owners: [<null>:52]
      Write lock owner: null
      ; - nested throwable: (org.jboss.cache.lock.TimeoutException: lock could not be acquired after 15000 ms. Lock map ownership Read lock owners: [<null>:52]
      Write lock owner: null
      )
      at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3266)
      at org.jboss.cache.TreeCache.put(TreeCache.java:1767)
      at org.jboss.cache.TreeCache.put(TreeCache.java:1750)
      at org.jboss.test.cache.stress.EvictionLocalStressTestCase$RunThread.op3(EvictionLocalStressTestCase.java:231)
      at org.jboss.test.cache.stress.EvictionLocalStressTestCase$RunThread._run(EvictionLocalStressTestCase.java:188)
      at org.jboss.test.cache.stress.EvictionLocalStressTestCase$RunThread.run(EvictionLocalStressTestCase.java:169)
      Caused by: org.jboss.cache.lock.TimeoutException: lock could not be acquired after 15000 ms. Lock map ownership Read lock owners: [<null>:52]
      Write lock owner: null
      at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:146)
      at org.jboss.cache.Node.acquireWriteLock(Node.java:422)
      at org.jboss.cache.Node.acquire(Node.java:388)
      at org.jboss.cache.TreeCache.findNode(TreeCache.java:3377)
      at org.jboss.cache.TreeCache._put(TreeCache.java:2367)
      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      I see the similar failures on a single proc winxp system with a pentium 4 with hyperthreading.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ben.wang Ben Wang (Inactive)
                  Reporter:
                  starksm64 Scott Stark
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: