Strange behavoir after an upgrade from 2.1 to 2.3.1 (timeout's occurs mor often)

[GoogleCodeExporter]

Hello everybody,

first of all a great memcache client implementation!

I had some strange behavoir after i updated from 2.1 to 2.3.1 version
I got a lot of more 

Caused by: java.util.concurrent.TimeoutException: Timed out waiting for
operation
    at
net.spy.memcached.MemcachedClient$OperationFuture.get(MemcachedClient.java:1656)
    at net.spy.memcached.MemcachedClient$GetFuture.get(MemcachedClient.java:1708)
    at com.zanox.cache.providers.MemCache.get(MemCache.java:107)
    ... 30 more

TimeoutException.

After a while i see that the reason is not the cache server or the network 
the new version 2.3.1 cause it. I have some couple of applications running
on the same server and they are using different version of spy memcached
library (2.1 and 2.3.1) and the timeout's occurs more often with the 2.3.1
version.

Original issue reported on code.google.com by pussinbo...@googlemail.com on 17 Jun 2009 at 1:59

• Merged into: #68

[GoogleCodeExporter]

After a long investigation the problem doesn't occurs after the version update
but it still exists and it seems that its a bug in the LinkBlockingQueue
implementation from sun. 

Here some logging of the spy logger

 2009-06-19 20:23:50,546 INFO Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - sun.nio.ch.SelectionKeyImpl@189ed00 has 
4,
interested in 5
 2009-06-19 20:23:50,546 INFO Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - sun.nio.ch.SelectionKeyImpl@189ed00 has 
a
ready op, handling IO
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - Handling IO for: 
sun.nio.ch.SelectionKeyImpl@189ed00 (r=false, w=true, c=false, op={QA sa=, 
#Rops=18,
#Wops=158, #iq=0, 
topRop=net.spy.memcached.protocol.ascii.GetOperationImpl@1648a2,
topWop=net.spy.memcached.protocol.ascii.StoreOperationImpl@1261dd2, 
toWrite=11206,
interested=5})
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Buffer is full, 
skipping
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Wrote 0 bytes
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Buffer is full, 
skipping
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Setting interested 
opts to 5
 2009-06-19 20:23:50,546 INFO Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - sun.nio.ch.SelectionKeyImpl@1cdaad2 has 
4,
interested in 5
 2009-06-19 20:23:50,546 INFO Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - sun.nio.ch.SelectionKeyImpl@1cdaad2 has 
a
ready op, handling IO
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - Handling IO for: 
sun.nio.ch.SelectionKeyImpl@1cdaad2 (r=false, w=true, c=false, op={QA sa=, 
#Rops=18,
#Wops=162, #iq=0, 
topRop=net.spy.memcached.protocol.ascii.GetOperationImpl@4bad63,
topWop=net.spy.memcached.protocol.ascii.StoreOperationImpl@1addae1, 
toWrite=13100,
interested=5})
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Buffer is full, 
skipping
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Wrote 0 bytes
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Buffer is full, 
skipping
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.protocol.ascii.AsciiMemcachedNodeImpl - Setting interested 
opts to 5
 2009-06-19 20:23:50,546 DEBUG Memcached IO over {MemcachedConnection to }
net.spy.memcached.MemcachedConnection - Done dealing with queue.

So the queue got overfilled. Any suggestion

Original comment by pussinbo...@googlemail.com on 19 Jun 2009 at 7:32

[GoogleCodeExporter]

Do you know if these ever answer?

Original comment by dsalli...@gmail.com on 13 Aug 2009 at 7:29

[GoogleCodeExporter]

I think I've found a likely root cause of these.

Original comment by dsalli...@gmail.com on 27 Oct 2009 at 4:23

• Changed state: Duplicate