Issue with Enyim client version 2.4
Hi,
Having used the MembaseClient in the v2.0b2 Enyim lib for a week or so without any issue we released an update to our service which uses v2.4 of the Enyim lib and started seeing some weird behaviour:
- some of the servers will lose their ability to talk to the cache server (seemingly around the same time) and not able to reconnect again
- reinitializing the Membase client doesn't work either, continues to get timeout exceptions when trying to get a socket from each of the pool urls (there were 4)
- putting the pool url [url]http://xxx:8080/pools/default[/url] in the browser works
- restarting our service fixed the problem
The problem also seems to resurface after a few hours and the only way to fix it was to restart our service..
The problem seems to be gone now that we've rolled back to the previous version of the Enyim library so it seems to reside with the new version of the Enyim client.
I'm just wondering if you guys have any further insight into this issue and if a workaround exists.
Thanks,
Can you please try this version?
[url]http://drop.io/wstg65g/asset/northscale-store-2-4-25-gd2c8b0d-zip[/url]
Additionally you can reach me at "a@enyim.com" if you feel email is faster than forums.
one more question i forgot to ask. how are you using the client?
a) one static instance per bucket
b) one instance per thread
c) using(client) { client.store(..); }
Hi Attila, thanks for getting back, will try out the version you sent and re-run our tests, as for your second question, we're running one static instance per bucket and we have two such static instances in our service.
Thanks for the feedback, we're looking into it now.
Perry
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!