Skip to content

Conversation

@Ian1971
Copy link

@Ian1971 Ian1971 commented Apr 26, 2012

This was because when the response was being read the response was not closed at the end. This meant that after 12xnumber cpu cores requests we were out of connections and just got timeouts.

@soitgoes
Copy link
Owner

Good catch. The only place it is needed though is in the GetResponsestring. I'll make the change e when I get to work

@Ian1971
Copy link
Author

Ian1971 commented Apr 26, 2012

I see, GetResponseStream closes the connection when the Stream closes.

@nsainaney
Copy link
Contributor

The other place I can think of is ViewResult. Perhaps this should implement IDisposable and close the HttpWebResponse there.

Update: Oops. I see you're modifying the Extension class and not the CouchDatabase/ViewResult. If so, I'd recommend an optional argument (e.g. public static Document GetCouchDocument(this HttpWebResponse response, bool closeResponse=true)) so the extension methods don't carry the business logic of closing the connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants