Bug 41239 - ServicePointManager is not getting cleaned up
Summary: ServicePointManager is not getting cleaned up
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-05-22 14:08 UTC by Alex Stefan
Modified: 2016-05-25 08:21 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Alex Stefan 2016-05-22 14:08:09 UTC
Hello,

I recently got into an issue on our Xamarin.Android apps.
Problem:

     - ServicePointManager.DefaultConnectionLimit has default values = 2
     - For different reasons those 2 concurent connections get faulted and after this, every request to the server is getting timeout error, but it doesn't reach the server
     - When setting up the DefaultConnectionLimit to 200, the bug it doesn't seem to reproduce. Therefor I'm thinking that the faulted connections are not cleaned up when they should.

I took a look into the ServicePointManager.cs from the referencesource and it looks like the "IdleServicePointTimeoutCallback" is missing from the mono code, but it seems to be exactly what may fix the problem.
How should I fix this?

Thank you,
Alex

Note You need to log in before you can comment on or make changes to this bug.