This is a regression. I have created an issue in JIRA: ISPN-2773
I don't think the client is ok, though: it seems to access the default cache, even though the default cache is not clustered. With HotRod you don't know which server you're accessing with a particular operation, so this could lead to unexpected results.
Thanks Dan for your prompt reply.
Here is my client code along with the configuration files and client log attached. From client I am trying access the namedCache i.e., distributedCache. not the default cache. Though client ran as expected except this exception that it received from server that comes as a response.
Ok, it's a bit late for a workaround now, as ISPN-2773 was fixed in 5.2.0.Final.
But for future reference, when the client opens a new connection to the server, it checks that the default cache is accessible. You can disable this by setting infinispan.client.hotrod.ping_on_startup=false in the HotRod client properties.