Looks like Memcached ClientLibrary used in the Memcached Cache
Provider that shipped with NHibernate 2.1.2 (and older) has issues
with Memcached 1.4.4 (and newer)
Here's the error I'm getting:
1.Error deleting key: x...@yyyy#121271. Server response: CLIENT_ERROR
bad command line format. Usage: delete <key> [noreply]
>From what I read in memcached release notes 1.4.4, looks like
Memcached 1.2.x used to support so called lingering delete. This is
when the client sends the delete command with an optional timeout
parameter set to a non-zero value. This causes the server to flag the
item as deleted but still keep in the cache (until the timeout
expires) -- this way the subsequent add operations would fail. This
rather obscure feature was removed completely in 1.4.0, but 1.4.4
introduced a backwards compatibility change that allows the timeout
value of 0 (i.e. non-lingering delete), while continuing to reject
others.
But why would Memcached ClientLibrary use the lingering delete
feature?! Looking at the sources here's what I see:
1.public bool Delete(string key)
2.{
3. return this.Delete(key, null, DateTime.MaxValue);
4.}
Clearly the DateTime.MaxValue is a problem. Looking at
http://sourceforge.net/projects/memcacheddotnet/ SVN I don't see this
fixed yet. What is the procedure for submitting a patch or getting
write access to memcacheddotnet repo?
--
You received this message because you are subscribed to the Google Groups
"NHibernate Contrib - Development Group" group.
To post to this group, send email to nhcd...@googlegroups.com.
To unsubscribe from this group, send email to
nhcdevs+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/nhcdevs?hl=en.
