Hi everyone
I've seen that Redis Stack Exchange releases Socket Failure through RedisConnectionException but I do not know where to start investigating this. Anyone have suggestions?
Exception: StackExchange.Redis.RedisConnectionException - SocketFailure on GET
at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor`1 processor, ServerEndPoint server) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\ConnectionMultiplexer.cs:line 1836
at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor`1 processor, ServerEndPoint server) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\RedisBase.cs:line 80
at StackExchange.Redis.RedisDatabase.StringGet(RedisKey key, CommandFlags flags) in c:\TeamCity\buildAgent\work\3ae0647004edff78\StackExchange.Redis\StackExchange\Redis\RedisDatabase.cs:line 1451
I am also having the same exception but no clue...
@NickCraver: Any suggestions or solution?
StackExchange.Redis.RedisConnectionException: SocketFailure on GET --->
System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.Security.SslStream.EndRead(IAsyncResult asyncResult)
at StackExchange.Redis.PhysicalConnection.EndReading(IAsyncResult result)
--- End of inner exception stack trace ---
at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor`1 processor, ServerEndPoint server)
at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor`1 processor, ServerEndPoint server)
at StackExchange.Redis.RedisDatabase.StringGet(RedisKey key, CommandFlags flags)
at StackExchange.Redis.Extensions.Core.StackExchangeRedisCacheClient.Get[T](String key)
did anyone identify the problem here? We are seeing this against azure hosted redis
So far there is no update on this issue. I am waiting since Feb....
Any updates on this?
I have the same problem. It seems the connection is corrupted and StackExchange.Redis doesn't try to reconnect automatically. Any solution?
We haven't been able to repro this on demand to nail it down. We know it is
causing intermittent problems, and it is on "the list". Hopefully should be
able to carve out some time to have another look in the new year. Parallel
with this, there is also ongoing work to overhaul the entire network core -
although this is mixed in with the "pipelines" work for asp.net, so no
current release date on that (it is still in evolution). The point being:
it is hoped that this work will stabilise this oddness.
On 29 Dec 2017 5:20 pm, "Theboss83" notifications@github.com wrote:
I have the same problem. It seems the connection is corrupted and
StackExchange.Redis doesn't try to reconnect automatically. Any solution?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/StackExchange/StackExchange.Redis/issues/556#issuecomment-354474324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABDsLKpBBsTBePeRtNLD68AElmgtMhkks5tFR9lgaJpZM4Lor_f
.
Most helpful comment
We haven't been able to repro this on demand to nail it down. We know it is
causing intermittent problems, and it is on "the list". Hopefully should be
able to carve out some time to have another look in the new year. Parallel
with this, there is also ongoing work to overhaul the entire network core -
although this is mixed in with the "pipelines" work for asp.net, so no
current release date on that (it is still in evolution). The point being:
it is hoped that this work will stabilise this oddness.
On 29 Dec 2017 5:20 pm, "Theboss83" notifications@github.com wrote: