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

Jump to bottom

RedisPubSubConnectionImpl.activated does not call super.activated() #55

Closed
mp911de opened this issue Apr 30, 2015 · 0 comments
Closed

RedisPubSubConnectionImpl.activated does not call super.activated() #55

mp911de opened this issue Apr 30, 2015 · 0 comments
Labels
type: bug A general bug
Milestone
Lettuce 3.2

Comments

@mp911de
Copy link
Collaborator

mp911de commented Apr 30, 2015

Connection activation, after reconnects, causes in RedisPubSubConnectionImpl to connect to the default database with no login, even if a previous login was performed. This is, because RedisPubSubConnectionImpl.activated does not call super.activated()
@mp911de mp911de added the type: bug A general bug label Apr 30, 2015
mp911de added a commit that referenced this issue May 4, 2015
@mp911de
Call super.activated() in PubSub Connection #55
b674c6d 
This change will restore database and authentication context when a pubsub connection is reconnected.
@mp911de mp911de closed this as completed May 4, 2015
@mp911de mp911de added this to the Lettuce 3.2 milestone May 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug A general bug
Projects
None yet
Milestone
Lettuce 3.2
Development

No branches or pull requests
1 participant
@mp911de