[infinispan-issues] [JBoss JIRA] (ISPN-2062) CrashedMemberDetectorListener should check whether invocations are allowed

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700817#comment-12700817 ] 

RH Bugzilla Integration commented on ISPN-2062:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> made a comment on [bug 760895|https://bugzilla.redhat.com/show_bug.cgi?id=760895]


    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,3 @@
-Tristan will provide CCFR or will route to appropriate developer.+Occasionally, when shutting down nodes in a cluster, the following message is reported: 
+"ERROR [org.infinispan.server.hotrod.HotRodServer] ISPN006002: Error detecting crashed member: java.lang.IllegalStateException: Cache '___hotRodTopologyCache' is in 'STOPPING' state and this is an invocation not belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate the cache container."
+This is due to the fact that a node has detected another node's shutdown and is attempting to update the topology cache while itself is also shutting down. The message is harmless, and it will be removed in a future release
                
> CrashedMemberDetectorListener should check whether invocations are allowed
> --------------------------------------------------------------------------
>
>                 Key: ISPN-2062
>                 URL: https://issues.jboss.org/browse/ISPN-2062
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Cache Server
>    Affects Versions: 5.1.4.FINAL, 5.1.5.CR1
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.5.FINAL
>
>
> Instead of just checking whether the cache is terminated, since this check misses other situations such as stopping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira