[infinispan-issues] [JBoss JIRA] (ISPN-9667) DefaultCacheManager inconsistent status checks

[Dan Berindei (Jira)]

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

Dan Berindei updated ISPN-9667:
-------------------------------
              Status: Pull Request Sent  (was: Reopened)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/6372, https://github.com/infinispan/infinispan/pull/6714  (was: https://github.com/infinispan/infinispan/pull/6372)


> DefaultCacheManager inconsistent status checks
> ----------------------------------------------
>
>                 Key: ISPN-9667
>                 URL: https://issues.jboss.org/browse/ISPN-9667
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 9.4.1.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Major
>             Fix For: 9.4.2.Final, 10.0.0.Alpha1
>
>
> {{DefaultCacheManager.getTransport()}} returns {{null}} when the manager is stopping, it should not. 
> To make things worse, {{DefaultCacheManager.getStatus()}} returns the status of the {{GlobalComponentRegistry}}, which is still {{RUNNING}} while caches are shutting down. That means {{DCM.getTransport()}} and {{DCM.getAddress()}} return {{null}} while the cache are stopping, and breaks distributed streams on caches that are still running.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)