This repository was archived by the owner on Dec 24, 2022. It is now read-only.
made idle timeout settable#183
Merged
mythz merged 1 commit intoServiceStack:masterfrom Sep 19, 2013
mhanney:master
Merged
Conversation
Member
|
Can you approve the Contributor License Agreement so we can include this, thx. |
Author
|
This is done, Thanks, On Thu, Sep 19, 2013 at 3:09 PM, Demis Bellot notifications@github.comwrote:
......... __ o |
Member
|
great, thx. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am using ServiceStack.Redis PooledRedisClientManager with redistogo.com. Redistogo closes idle client connections after 150 seconds (on the small plan). The current default idle timeout in ServiceStack.Redis is hard set at 240 seconds. This results in "No more data" exceptions when using a connection from the pool that has been closed by the server. Lowering the idle time out to < 150 (for redistogo) fixes this because RedisNativeClient.AssertConnectedSocket does the necessary checks and reconnects the client.