Can you add an assert within client.set or asyncGet if there're any
newlines, spaces, etc in userRequest?
Sorry, missed your response last week :(
On Tue, 20 Feb 2018, Praveen wrote:
> Thanks again Dormando for your quick inputs on this issue.
>
> The protocol we are using is Text. Below is
Thanks again Dormando for your quick inputs on this issue.
The protocol we are using is Text. Below is the code of
ConnectionFactoryBuilder and other parts in setting and retrieving the data:
--
Hey,
I believe what you're seeing, however I'm telling you how this happens.
There hasn't ever been a server-side bug where a key gets set to the wrong
value. It's possible, if the protocol is corrupted, for garbage data to
end up in a value, and only with the ascii protocol. Though you said you
Thanks Dormando for your prompt responses on this.I really appreciate it.
The server running on docker is on top of alphinelinux.
I am able to reproduce the issue in local dev environment but I am not much
worried in local dev as it is used only for development and Unit Testing.
Keys will have
Thanks Dormando for your prompt responses on this.I really appreciate it.
The server running on docker is on top of alphinelinux.
I am able to reproduce the issue in local dev environment but I am not much
worried in local dev as it is used only for development and Unit Testing.
Keys will have
Hey,
Oh, we don't actually support windows. That might be an old fork/port. Is
the server running in docker on top of linux?
Are you reproducing the issue in your local dev environment?
like I said before; most likely you need to examine the kind of keys
you're setting. Make sure they're only
Thank you for your thoughts on this Dormando.
I need to check with my team for the version in the docker container but in
my local dev environment memcached version is 1.4.5_4_gaa7839e where the OS
is Windows 7 and I am running my app in Eclipse.
Once key1 returns wrong data then the same
Just out of curiosity; what version of the server are you running?
This is always an issue with your client code.
1) if you telnet directly to memcached and run "get key1", does it return
abc or 123?
2) if abc, then you might have an ordering issue or invalid characters in
your keys (\n, space,
What could be the reason for memcached to return wrong value?
Ex: Key1 -> "abc"; key2 -> "123".
When I am trying to retrieve data for Key1, data returned is 123 instead of
abc. This happens in my local environment(application on Windows machine
with memcached-win64) and also in dev
