Cache managers failing to start do not stop global components ------------------------------------------------------------- Key: ISPN-6391 URL: https://issues.jboss.org/browse/ISPN-6391 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.2.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.1.Final, 9.0.0.Alpha1, 9.0.0.Final 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).