You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously it was working normal and happens after some time. I've checked the source codes and think this can be caused by 2 ways:
The connection wasn't open previously. I've checked and everything is fine here.
The connection was closed by some thread and JRedisService serves it as a new for future clients. E.g. in SynchConnection I can see that we close the connection in case of exception during serviceRequest() such as: ProviderException, RuntimeException. Looks reasonable that if we want to use this connection for other requests (as it happens in JRedisService) in future, we shouldn't close it in that way. Or make sure to return open connection in JRedisService (maybe in kind of option, e.g. reconnectAutomaticly).
My proposal is to check that JRedisService returns the open connection. And if it's closed, do the automatic reconnect.
The text was updated successfully, but these errors were encountered:
I am expecting connection issues while working with redis thought JRedisService. It just says that the used connection is not connected:
Apr 18 23:12:54 tomcat12 tomcat-jqc-app: : Not connected!
Apr 18 23:12:54 tomcat12 tomcat-jqc-app: : org.jredis.ri.alphazero.connection.SynchConnection.serviceRequest(SynchConnection.java:122)
Apr 18 23:12:54 tomcat12 tomcat-jqc-app: : org.jredis.ri.alphazero.JRedisService.serviceRequest(JRedisService.java:179)
Apr 18 23:12:54 tomcat12 tomcat-jqc-app: : org.jredis.ri.alphazero.JRedisSupport.set(JRedisSupport.java:379)
Apr 18 23:12:54 tomcat12 tomcat-jqc-app: : org.jredis.ri.alphazero.JRedisSupport.set(JRedisSupport.java:383)
Previously it was working normal and happens after some time. I've checked the source codes and think this can be caused by 2 ways:
My proposal is to check that JRedisService returns the open connection. And if it's closed, do the automatic reconnect.
The text was updated successfully, but these errors were encountered: