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.

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

Handle exceptions on close in JedisSentinelPool #2102

Merged
merged 1 commit into from Nov 24, 2019

Conversation

Talon876
Copy link
Contributor

@Talon876 Talon876 commented Nov 22, 2019

When returning a Jedis object to the pool, handle any exceptions and still return the connection to prevent deadlock.
This is similar to issue and fix for #791, but for the JedisSentinelPool.

When returning a Jedis object to the pool, handle any exceptions and still
return the connection to prevent deadlock.
This is similar to issue redis#791 but for the JedisSentinelPool.
@Talon876 Talon876 changed the title Handle exceptions on close Handle exceptions on close in JedisSentinelPool Nov 22, 2019
@sazzad16
Copy link
Collaborator

LGTM!

@devil5462
Copy link

@sazzad16 Hi, mate. Thanks for this Issue to solve. I faced that like you. However, I am using version Jedis 2.9.0. I understand version 2.10.2 is latest in version 2. Is it work well or a fixed issue?( #1819 ) I have to use version 2. Let me know the way to use in version 2. I'm looking forward to your reply.

@sazzad16
Copy link
Collaborator

sazzad16 commented Nov 6, 2020

@devil5462 yes, this merged PR solved connection leaking issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants