Closed raymondsiu99 closed 1 day ago
Hello, I don't know if I can help you with this report. I cannot reproduce it as you didn't provide any steps to reproduce the issue, and I don't have access to Azure anyway.
It looks like connection misconfiguration but hard to tell without knowing any details.
I believe this is an issue of the configuration but if it is an issue with the underlying connector then you are using an outdated version with rediscala under the hood, which unfortunately has no support from their maintainers, which is why the latest versions of play-redis switched to a different connector.
My recommendation is to properly debug your setup and/or provide minimal steps to reproduce the issue (with docker) and/or updating to the latest versions of play-redis.
Thanks for your reply; I will recommend my team to update the library; in the meantime I will just deploy redis in AKS for test.
Are you filing an issue? Please follow these checklists and provide us all the possible information to speed up the process.
Reporting a bug?
Inject by
configured some thing like
Got exception like:
Other notes: The Azure Cache for Redis was tested within the container by executing redis-cli