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

Cache managers failing to start do not stop global components

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.2.1.Final, 9.0.0.Final
    • 8.2.0.Final
    • Core
    • None

      If one of the global components fails to start, GlobalComponentRegistry.start() removes the volatile components, but it doesn't call stop() on those components.

      The most likely reason for a global component start failure is a timeout in JGroupsTransport.waitForInitialNodes(). After such a timeout, the transport isn't stopped, so the channel's sockets and threads are only freed after a few GC cycles (via finalization).

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

                Created:
                Updated:
                Resolved:
                Archived: