-
Notifications
You must be signed in to change notification settings - Fork 24
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
Authentication doesn't work #67
Comments
@neilchaudhuri might confirm the issue rised since Brando 3.0.x. Based on play-redis#29 I guess it worked with Brando 2.x.x |
OK, I confirm myself, with Brando 2.1.2 it works as expected. |
is this is fixed ?? I'm still not able to connect
|
I think it's only on Damien's branch at the moment. check it out
then publish it with sbt or activator
Then you'll have v 3.0.4 available in your local sbt repository which you can use from your project for now. I'll have a look at the pull request later to see if I can help out. |
thanks for info.. I'm done it already for my project. in plan to switch to another library for play-redis because of repo is inactive |
I traced issues reported as Brando #64 and play-redis #44 and #29
Backstory
We noticed the first occurrence of the issue on Heroku because it secures its redis instance. It caused excessive logging without any reasonable error message.
However, I successfully reproduced in on localhost when I secured my redis instance.
How to reproduce
Enable redis authentication in redis.conf, e.g., uncomment
Code reproducing the issue
Example of Play framework controller:
Observation
When used
Redis
actor the response is the redis is disconnected. When theStashingRedis
is used, requests timeout. Both no further reason provided.Tracing the issue
To trace the issue, I inserted several logging statements into Brando. I figured out two things:
auth
is provided. The reason is it stucks inConnecting
state but the authentication is executed onConnected
.Subsequent issues
When max number of clients is reached, it crashes at this line.
Finally, it goes out of memory after while. However, I am not sure what exactly causes the memory leaking, just guessing.
The text was updated successfully, but these errors were encountered: