Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-837

Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork()

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • 4.17.0
    • 4.14.0
    • None
    • None
    • Hide

      I've changed our JBoss JTA configuration to use HashedStore instead of CacheStore for now. We are using CacheStore in hopes of getting the best transaction performance.

      Show
      I've changed our JBoss JTA configuration to use HashedStore instead of CacheStore for now. We are using CacheStore in hopes of getting the best transaction performance.

      Our product has a scheduled job that runs every 30 minutes. Callable instances are added to an ExecutorService instance which is currently configured for 16 threads.

      Our JBoss JTA implementation is using CacheStore as the object store (default-jbossts-properties.xml attached).

      After some time a NoSuchElementException is thrown from AsyncStore.doWork(). That exception is somehow blocking other transaction thread's execution.

      The Java thread dump is attached as well.

        1. arjuna-deadlock-trace.txt
          77 kB
        2. default-jbossts-properties.xml
          7 kB
        3. default-jbossts-properties.xml
          7 kB
        4. NonblockingCacheStore.zip
          5 kB

            thjenkin@redhat.com Tom Jenkinson
            tomwaterhouse_jira Tom Waterhouse (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: