Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-6977

NumOwnersNodeCrashInSequenceTest random failures

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • 9.0.0.Final
    • 8.2.4.Final, 9.0.0.Final, 10.1.5.Final, 11.0.0.Dev03
    • Core

      The test (and NumOwnersNodeStopInSequenceTest as well) uses StateSequencerUtil.advanceOnInboundRpc(), which replaces the PerCacheInboundInvocationHandler and rewires all the components.

      The problem is that rewiring StateConsumerImpl causes it to create a new SemaphoreCompletionService, but there's no synchronization when reading the field, a "background" task could finish on another thread and release the permit on the old SemaphoreCompletionService instance.

              dberinde@redhat.com Dan Berindei (Inactive)
              dberinde@redhat.com Dan Berindei (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: