[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Manik Surtani updated ISPN-611: ------------------------------- Fix Version/s: 4.1.0.Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-611: ------------------------------------ Would be great if you can provide a Ruby script that we can run on the command line to reproduce this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Tomaz Cerar updated ISPN-611: ----------------------------- Attachment: infinispan_memcached.log Hi guys, We are preparing sample ruby script to demonstrate error. In attachment you can find full stacktrace that I can found in "infinispan_test.log" file in bin folder. I run infinispan from all distribution with default script "./startServer.sh -r memcached" I can enable additional logging if it would help you. the broken pipe exception i think comes from client forcefully closing connection to server when invalid response is recived. from client log: D, [2010-08-19T13:37:58.455827 #21027] DEBUG -- : get objects/all_sections from <MemCache::Server: localhost:11211 [1] (NOT CONNECTED)> W, [2010-08-19T13:37:58.462348 #21027] WARN -- : Generic failure: MemCache::MemCacheError: unexpected response "VALUE objects/all_sections 0 166188 \r\n" W, [2010-08-19T13:37:58.466978 #21027] WARN -- : Generic failure: MemCache::MemCacheError: unexpected response "VALUE objects/all_sections 0 166188 \r\n" D, [2010-08-19T13:37:59.380948 #21020] DEBUG -- : set objects/all_sections to <MemCache::Server: localhost:11211 [1] (NOT CONNECTED)>: 166188 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Tomaz Cerar commented on ISPN-611: ---------------------------------- Hi, we are using memcache-client http://rubygems.org/gems/memcache-client version 1.7.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreno commented on ISPN-611: --------------------------------------- Just tried Spymemcached 2.5 (http://code.google.com/p/spymemcached/downloads/list), which is latest and still does not like this. I've tried the test python scripts we have and they work fine with either version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreno commented on ISPN-611: --------------------------------------- The memcached protocol is not very clear in this area - http://code.sixapart.com/svn/memcached/trunk/server/doc/protocol.txt "Each item sent by the server looks like this: VALUE <key> <flags> <bytes> [<cas unique>]\r\n <data block>\r\n " If 'cas unique' came, one would assume no space would be between the end of the version and \r\n. If no 'cas unique' was given, would a space be needed after bytes? I can't say which of the two client libraries is right, but one thing is for sure, both of them are being a bit too strict in this area. Tomas, can you guys try with a different Ruby memcached client library? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Tomaz Cerar commented on ISPN-611: ---------------------------------- Hi, we will try with different client, I will post results how it goes. Strange thing is that we currently as server use memcached 1.4.5 "the official" server impl. That is why I asked if you tried spymemcached against this one? Maybe bug is only in spymemcached, but it is more possible that it exists in ruby memcache-client.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreno commented on ISPN-611: --------------------------------------- Tomas, just fixed the issue. The correct way is indeed without the trailing space. The problem with Spymemcached was that once I removed the trailing space, I also removed the separation with cas_unique and so some tests failed. It's all good now. The issue will be fixed for 4.1.0.Final. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-611?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreno resolved ISPN-611. ----------------------------------- Resolution: Done Tomas, the issue is fixed in both 4.1.x branch and trunk. Build 4.1.x branch and try it out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira