Get canceled about spymemcached HOT 5 CLOSED

This doesn't look like an error. Your get operation was cancelled because the 
client got disconnected from the server. Also, the get function just calls 
asyncGet() and calls get() on the Future that is returned so if there is an 
issue here calling asyncGet() over get() won't help you.

Can you provide more detail on the problem if you still think there is an issue 
with the client.

hmmm.. it's weird that it couldn't reconnect until I restarted the entire app. 
It kept repeating that same step. Have any ideea why?

I think I misinterpreted the error you were trying to communicate. Is the issue 
that when the client gets disconnected from the server it is unable to connect? 
If so this is something I will look into because that shouldn't happen.

Can you tell me what you are doing in your application code?

I opened 3 clients (each with another server) and used a weighted roundrobin 
distribution on them for setting, but mostly for getting. It tried a 'get' 
every one second.It got about 30 items per min. When this error appeared, It 
kept trying to reconnect until i restarted it. The detail that i don't missed 
to remember is if it tried to reconnect for one or for all servers(but I think 
it was for the server that was next to be read). I switched to gwhalin's 
version because of failover and failbacks. All the best. Mihai

We're pretty confident reconnection works, it's in our automated test suite and 
we've tested with a similar client.  There were a couple minor thread safety 
issues fixed recently.  As best I can tell, it may have been one of those.  

If there's any more info available, please let us know.