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

Deadlock during server start

    XMLWordPrintable

Details

    Description

      This happens frequently when starting servers in parallel, the more servers, the easier to reproduce.
      Attached the stack trace of server1 and server2 after hanging.

      Attachments

        1. s0.txt
          296 kB
        2. s1.txt
          86 kB
        3. server1.txt
          143 kB
        4. server2.txt
          131 kB

        Issue Links

          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-4625 Deadlock during server start

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is incorporated by

          Task - A task that needs to be done. ISPN-6433 Backport to 8.1.x branch

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JDG-147 Deadlock during server start

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. ISPN-6195 CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. ISPN-6746 Server instances fail to boot with WARN messages

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dberinde@redhat.com Dan Berindei (Inactive)
              gfernand@redhat.com Gustavo Fernandes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: