3 Replies Latest reply on Mar 15, 2012 11:51 AM by Galder Zamarreño

    hotrod client topology not updated in 5.1.0 FR

    henners Newbie

      some questions


      1. I have two infinispan instances in a cluster.. I kill one of them.. The client keeps reporting java.netConnection exceptions and never considers the topology changed... Is that expected behaviour ?


      2. when the killed instance restarts the client gets informed that there is a new topology but that the restarted one is removed .. So then it never gets informed that both the members are in the cluster.

         This is obviously not intended behaviour.. So my question is is this known/fixed in 5.1.2 ?