-
Notifications
You must be signed in to change notification settings - Fork 990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SslClosedEngineException
thrown after exceeding connection init timeout
#2023
Comments
The problem came again after I did another test today. But it seems the connection failed at the first operation after app getting started. At second operation, suddenly the app was able to reconnect to the remote instance . It seems the issue is on the SSL handshake. How to solve this?
So, somehow reconnecting is fine, but standard/regular connecting attempt always fails. |
I think I found the root cause. I set the commandTimeout as 100ms. It seems it's being used to establish connection and it's not enough to verify the connection. Can we separate command timeout and connection timeout. I really need that command timeout as I have a use case to fail redis get and set operation as soon as possible if there is a connection issue. |
I've seen a couple requests to configure the handshake timeout. I wonder whether it makes more sense to use the connect timeout as handshake timeout. |
SslClosedEngineException
thrown after exceeding connection init timeout
…#2023 We now suppress exceptions thrown by e.g. the SSL handler when RedisHandshakeHandler enters timeout handling to surface the expected timeout exception.
@mp911de : What needs to be done to get rid of the SSLClosedEngineException in 6.1.8.RELEASE version of lettuce-core? We are also facing the same exception but could not understand what was the fix that was called out or atleast unable to conclude that from various threads. Can you please help us understand? |
Bug Report
Current Behavior
Summary: Connection to remote Redis failed due to "Cannot obtain initial Redis Cluster topology".
Stack trace
Input Code
Input Code
Expected behavior/code
Able to connect my app to the Elasticache instance.
Environment
Possible Solution
Apparently, I needed to set up some custom factory.
Solution
Additional context
For context, currently I am building a service that will connect to a Elastisearch Redis instance. I am using Reactive Spring Boot (WebFlux).
I tested in local using simple Redis instance in docker and it was working.
The text was updated successfully, but these errors were encountered: