Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JredisService connection reset handling #6

Closed
fabriziobonavita opened this issue Nov 22, 2009 · 1 comment
Closed

JredisService connection reset handling #6

fabriziobonavita opened this issue Nov 22, 2009 · 1 comment
Labels
defect

Comments

@fabriziobonavita
Copy link

JRedisService does handle idle connection resets but doesn't consider the number of connections configured before - only uses one connection after reconnect.
@alphazero
Copy link
Owner

JRedisService connections each get their own dedicated heartbeat now. This should no longer be an issue. (Tested with timeout of 3 secs on redis.conf.)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alphazero @fabriziobonavita