Hello, I've written a custom module that interacts with memcache using the apr_memcache library. I find that most of the time it works beautifully, but it seems to be giving me some problems now that I'm introducing some load in to the module.
What's happening is that after a period of time, all apr_memcache_set() calls are failing with APR_EGENERAL, presumably because the buffer from get_server_line() doesn't contain either "STORED" or "NOT_STORED", which doesn't make any sense: my memcached server is healthy, and I can clearly see "STORED" when sniffing packets between Apache and memcached. Sending a SIGHUP to the parent process clears things up, and apr_memcache_set() calls begin returning properly. I've been reading about the memory leak found in apr_memcache (http://issues.outoforder.cc/view.php?id=68), and I'm not sure whether or not my issue could possibly be caused by this. Has anyone had similar experiences? Thanks, Brooks
