.NET SDK Connection configuration that works fine on local user account fails in web application
We have a web application that uses an internal client library which wraps the Couchbase .NET SDK. In attempting to upgrade the system to use Couchbase Server 2.0, the wrapper library's caching functions tests work fine, but the web app's caching, with an identical configuration, does not work.
I attempted to upgrade the Couchbase Server to 2.0, and discovered that some changes were needed in the wrapper library. I updated the wrapper and ran through its tests - everything worked fine (including bucket flushing, which was updated to be implemented using the CouchbaseCluster class).
When I then built the wrapper and updated the web application, I discovered that almost none of the web app's caching functionality was working - basically, any calls to Store data did not insert anything into the cache, and any calls to Get data did not retrieve anything from the cache. The only functionality that worked was the updated Flush call, which did indeed flush the bucket as expected.
The configuration for the two applications (i.e. the tests for the wrapper, and the web application) is identical, yet the web application doesn't seem to be able to connect to the cache, except when flushing. It seems that the CouchbaseClient class is not connecting properly, while the CouchbaseCluster class is connecting fine.
Can anyone recommend a possible course of action to determine what the source of the problem is? We know that the CouchbaseClient uses a pooled socket connection while the CouchbaseCluster issues web requests through the HttpHelper class, but that is not necessarily related to the problem.
For now we will simply continue to use version 1.8.0, but obviously updating to a newer version is preferable, and we need to resolve this problem before we can do so.