[infinispan-issues] [JBoss JIRA] (ISPN-9220) Client listeners are sometimes re-registered twice after infinispan-server restart

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño updated ISPN-9220:
-----------------------------------
    Labels: redhat-summit-18  (was: )


> Client listeners are sometimes re-registered twice after infinispan-server restart
> ----------------------------------------------------------------------------------
>
>                 Key: ISPN-9220
>                 URL: https://issues.jboss.org/browse/ISPN-9220
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Hot Rod
>    Affects Versions: 9.2.1.Final
>            Reporter: Marek Posolda
>              Labels: redhat-summit-18
>
> During test of summit, we saw some issue with client listeners. Setup was this:
> - Every site had one hotrod client (RHSSO), which used infinispan of version 8.2.8.Final and one infinispan-server, which I think was version 9.2.1.Final
> - Client (RH-SSO) had some client listener registered against remoteCache
> - After restart of infinispan-server, the RH-SSO was able to re-connect to it and CRUD the items to the remoteCache. But previously registered clientListeners were lost.
> Note that setup demo used just 1 infinispan-server on every site, so there were not any topology changes (no possibility of re-balance client listener to other node).
> I've tried to do simple reproducer for the scenario above and verified that with client 8.2.8.Final and server 9.2.1.Final, the client listener is not automatically re-registered after restart. 
> BUT after upgrade client to 9.2.1.Final, re-registration worked fine and client listener was re-registered automatically. This is important as from long term perspective, we are upgrading to infinispan 9 on RH-SSO side. But I had the opposite issue, that sometimes the client listener is registered twice. See steps to reproduce for the details.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)