I assume you are running memcached in any kind of unix. So do you had the java virtual machine and the memcached runing in the box while you got those errors?. If so, forget about the network. But you could check how busy is your box when you start those threads (mem, cpu)
On the other hand, see the log in the memcached server. Start it like memcached <your usual configuration> -vv 2>/tmp/log and see what appears in the log file. Also see syslog file. On Thu, Feb 25, 2010 at 2:35 PM, mariyan nenchev <[email protected]> wrote: > > Every thing is one one machine in development, but it will be separate > server for the memcache with LAN. > Yes i tried it. What should i see? It stop updating the cache while i get > the exceptions above. > On Thu, Feb 25, 2010 at 6:31 PM, Carlos Alvarez <[email protected]> wrote: >> >> That's a problem, because a lot of issues have to do with clients. >> >> Anyway, how healthy is your network?. >> >> Have you tried running memcached with -vv (two 'v' and not a 'w' and) >> and see the log in the server? >> >> On Thu, Feb 25, 2010 at 1:56 PM, mariyan nenchev >> <[email protected]> wrote: >> > Hi, it is not up to me to change the client. >> > >> >> >> >> -- >> Quidquid latine dictum sit, altum sonatur. ;-) > > -- Quidquid latine dictum sit, altum sonatur. ;-)
