-
Bug
-
Resolution: Done
-
Major
-
None
-
9.4.23.Final, 11.0.11.Final, 12.1.7.Final
-
None
The client configuration setting infinispan.client.hotrod.socket_timeout controls how long the client waits for a response from the server.
Before switching to Netty, each operation had its own thread, so it was natural to close the connection after the timeout expired and hopefully save the server from sending a lot of data. But now that the client uses Netty, many other operations could be using the same server connection, and closing the channel will affect all of them:
2021-06-21 19:06:13,612 [HotRod-client-event-loop-group-3] ERROR org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation - ISPN004007: Exception encountered. Retry 0 out of 0 org.infinispan.client.hotrod.exceptions.TransportException: ISPN004071: Connection to server:11222 was closed while waiting for response.
- is related to
-
ISPN-12598 Hot Rod java client retries too many times
- Closed
- relates to
-
ISPN-13220 Initial server list switch should increment topology age
- Closed
-
ISPN-13264 Hot Rod client cluster switch never happens if max-retries < cluster size
- Closed