-
Notifications
You must be signed in to change notification settings - Fork 43
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
key in command for ExecutionFailedException #102
Comments
Hi @Enalmada, it seems like you hit several rough spots at once.
The first one is already fixed and I'll push it soon, the other one I have to investigate more deeply because brief code examination didn't reveal the cause. What version do you use? I need to know which version patch |
Oh, my bad. I misinterpreted this
Now I get it and look into it |
Hi, I use 1.5.0. I just upgraded to playframework 2.6 and needed something I could use on AWS for multiple servers. I was going to use memcached (since I didn't know any better) but that module is not yet updated to 2.6. I am so grateful that play-redis is 2.6 ready, thank you very much for your community contributions. Play-redis looks pretty nice so far! |
Thanks for the appreciation, I published the patch as |
I am using Kyro and trying to extend a the log and default recovery policy to delete the key that has a serialization issue.
When looking at the Reports trait, the message function says I get a ExecutionFailedException instead of the expected SerializationException i see later in the report stack trace.
Also, the key value seems to be the command and the command has " "seems to be appearing as part of the command and the command :
Command $command for key '$key' failed -> Command GET for key 'GET' failed.
The text was updated successfully, but these errors were encountered: