[infinispan-issues] [JBoss JIRA] (ISPN-6391) Cache managers failing to start do not stop global components

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-6391:
-------------------------------
    Status: Open  (was: New)


> 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: 9.0.0.Final, 8.2.1.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).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)