Smileyt / spymemcached

Automatically exported from code.google.com/p/spymemcached
0 stars 0 forks source link

Problem with shutdown #256

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What version of the product are you using? On what operating system?

Tell me more...

I've a problem with a memcached shutdown command. I reported my source:

InetSocketAddress scktAddress = new InetSocketAddress(host, 39999);
// Istance of memcached client
memcachedClient = new MemcachedClient(scktAddress);

// Store MyKey
memcachedClient.add("mykey", 0, new String("myvalue"));

.... other add/delete keys

At the end, when I finished to write and read in memcached area, send shutdown 
command:

memcachedClient.shutdown();

I receive this error message:

[09 ago 2012 12:05:36,318] DEBUG [?:?:?] - Completed read op: Cmd: get Keys: 
module_by_name_CACHEExp: 0 and giving the next 0 bytes
[09 ago 2012 12:05:36,318] DEBUG [?:?:?] - Setting interested opts to 0
[09 ago 2012 12:05:36,318] DEBUG [CacheStore.java:run:110] - Module: CACHE - 
ID: 2
[09 ago 2012 12:05:36,318] DEBUG [?:?:?] - Done dealing with queue.
[09 ago 2012 12:05:36,318] DEBUG [?:?:?] - Selecting with delay of 0ms
[09 ago 2012 12:05:36,319] DEBUG [CacheStore.java:run:123] - Shutdown memcached 
in progress...
[09 ago 2012 12:05:36,319] DEBUG [?:?:?] - Selected 0, selected 0 keys
[09 ago 2012 12:05:36,320] DEBUG [?:?:?] - Shut down channel 
java.nio.channels.SocketChannel[closed]
[09 ago 2012 12:05:36,320] DEBUG [?:?:?] - Exception occurred during shutdown
java.io.IOException: No IO while shut down
    at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:201)
    at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:833)
[09 ago 2012 12:05:36,322]  INFO [?:?:?] - Shut down memcached client
[09 ago 2012 12:05:36,320] DEBUG [?:?:?] - Shut down selector 
sun.nio.ch.WindowsSelectorImpl@9278d5

What is the meaning of the phrase: "No IO while shut down", as I have finished 
the process of writing and reading.

Thanks in advance, 
Mariusv5.

Original issue reported on code.google.com by sonnes...@gmail.com on 9 Aug 2012 at 10:08

GoogleCodeExporter commented 8 years ago
This means that we tried to handle IO while the connections were in the process 
of being shutdown. The fix for this should be trivial.

Original comment by mikewie...@gmail.com on 17 Aug 2012 at 5:45

GoogleCodeExporter commented 8 years ago
Is this still an issue with the latest libraries?

Original comment by michael....@gmail.com on 16 Oct 2013 at 2:02