Skip to content

DATAREDIS-531 - Fix deferred ScanCursor command execution using Jedis. #217

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

Closed
wants to merge 2 commits into from

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Aug 30, 2016

Previously, ScanCursor held a reference to the Jedis connection which was used during ScanCursor creation. Cursors can be used outside RedisTemplate that leads to releasing/closing the initial connection. The retained reference used a released connection.

We now check whether the connection is still open. If so, we reuse the connection. If the connection is closed, we use the associated connection factory to obtain a connection to invoke SCAN and release the reference after command execution.


Related ticket: DATAREDIS-531

Previously, ScanCursor held a reference to the Jedis connection which was used during ScanCursor creation. Cursors can be used outside RedisTemplate that leads to releasing/closing the initial connection. The retained reference used a released connection.

We now check whether the connection is still open. If so, we reuse the connection. If the connection is closed, we use the associated connection factory to obtain a connection to invoke SCAN and release the reference after command execution.
@mp911de
Copy link
Member Author

mp911de commented Sep 5, 2016

Superseded by #218.

@mp911de mp911de closed this Sep 5, 2016
@mp911de mp911de deleted the issue/DATAREDIS-531 branch September 5, 2016 09:23
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.

1 participant