Hot Rod client taking time to fail, when the backup server in cross-site is already down

Solution Unverified - Updated -


There are two clusters in a cross-site setup. The Hot Rod client is connected to the cross-site setup, where the RemoteCacheManager (RCM) is shared between the multiple threads. If the backup cluster is already down, and primary cluster also goes down. The hot rod client is ignoring the connection-timeout and taking time to throw an exception message.


Red Hat Data Grid 7.2.x.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In