Re: [Mono-dev] TCP connects

[Greg Young]

OK I spent some more time looking through this. There is a ton of not
really async stuff happening in async methods also
cancellations/timeouts/etc don't work properly. Moral of the story for
people searching this in the future etc, use the PCL version which
seems to work thus far.



On Thu, May 26, 2016 at 5:36 PM, Greg Young  wrote:
> In looking through a recent issue, when a node disappears we end up with:
>
> "Threadpool worker" at  <0x>
> at (wrapper managed-to-native)
> System.Net.Sockets.Socket.Connect_internal
> (intptr,System.Net.SocketAddress,int&) <0x>
> at System.Net.Sockets.Socket.Connect (System.Net.EndPoint) <0x00135>
> at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x00615>
> at System.Net.WebConnection.InitConnection (object) <0x0031a>
> at System.Net.WebConnection.m__0 (object) <0x00024>
> at (wrapper runtime-invoke)
> .runtime_invoke_void__this___object
> (object,intptr,intptr,intptr) <0x>
>
> "Threadpool worker" at  <0x>
> at (wrapper managed-to-native)
> System.Net.Sockets.Socket.Connect_internal
> (intptr,System.Net.SocketAddress,int&) <0x>
> at System.Net.Sockets.Socket.Connect (System.Net.EndPoint) <0x00135>
> at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x00615>
> at System.Net.WebConnection.InitConnection (object) <0x0031a>
> at System.Net.WebConnection.m__0 (object) <0x00024>
> at (wrapper runtime-invoke)
> .runtime_invoke_void__this___object
> (object,intptr,intptr,intptr) <0x>
>
> On every thread from our async code. As the connection is timing out
> the entire ThreadPool very quickly blocks.
>
> https://github.com/mono/mono/blob/master/mcs/class/System/System.Net/WebConnection.cs#L195
>
> I am guessing the right fix here would be to use async connect?
>
> Cheers,
>
> Greg
>
>
> --
> Studying for the Turing test



-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] TCP connects

[Greg Young]

In looking through a recent issue, when a node disappears we end up with:

"Threadpool worker" at  <0x>
at (wrapper managed-to-native)
System.Net.Sockets.Socket.Connect_internal
(intptr,System.Net.SocketAddress,int&) <0x>
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint) <0x00135>
at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x00615>
at System.Net.WebConnection.InitConnection (object) <0x0031a>
at System.Net.WebConnection.m__0 (object) <0x00024>
at (wrapper runtime-invoke)
.runtime_invoke_void__this___object
(object,intptr,intptr,intptr) <0x>

"Threadpool worker" at  <0x>
at (wrapper managed-to-native)
System.Net.Sockets.Socket.Connect_internal
(intptr,System.Net.SocketAddress,int&) <0x>
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint) <0x00135>
at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x00615>
at System.Net.WebConnection.InitConnection (object) <0x0031a>
at System.Net.WebConnection.m__0 (object) <0x00024>
at (wrapper runtime-invoke)
.runtime_invoke_void__this___object
(object,intptr,intptr,intptr) <0x>

On every thread from our async code. As the connection is timing out
the entire ThreadPool very quickly blocks.

https://github.com/mono/mono/blob/master/mcs/class/System/System.Net/WebConnection.cs#L195

I am guessing the right fix here would be to use async connect?

Cheers,

Greg


-- 
Studying for the Turing test
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list