By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,903 Members | 1,977 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,903 IT Pros & Developers. It's quick & easy.

BUG in non-blocking socket connect ?

P: n/a
Hi,

1. It seems to me that there is a bug when using non-blocking socket
connect operation, because the LocalEndPoint, RemoteEndPoint of the Socket
are nulls on the client side although that the client and the server are
already connected.

2. If it is a bug, is there any hotfix for this ?

Thanks.
Nov 17 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
Yaron,

Can you show a piece of code which demonstrates the bug? It sounds to
me that the socket is maintaining the reference even though the variables
you use are not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
Hi,

1. It seems to me that there is a bug when using non-blocking socket
connect operation, because the LocalEndPoint, RemoteEndPoint of the Socket
are nulls on the client side although that the client and the server are
already connected.

2. If it is a bug, is there any hotfix for this ?

Thanks.

Nov 17 '05 #2

P: n/a
Nicholas,

here is a link that talk on this problem.

http://www.dotnet247.com/247referenc...39/196138.aspx

Thanks.

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

Can you show a piece of code which demonstrates the bug? It sounds to
me that the socket is maintaining the reference even though the variables
you use are not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
Hi,

1. It seems to me that there is a bug when using non-blocking socket
connect operation, because the LocalEndPoint, RemoteEndPoint of the Socket
are nulls on the client side although that the client and the server are
already connected.

2. If it is a bug, is there any hotfix for this ?

Thanks.


Nov 17 '05 #3

P: n/a
Yaron,

I've read the thread, and it appears that MSFT is aware of the bug.
From what I know, there is no hotfix for this yet. It *might* have been
addressed in .NET 2.0, but you need to check the Product Feedback Center for
that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E5**********************************@microsof t.com...
Nicholas,

here is a link that talk on this problem.

http://www.dotnet247.com/247referenc...39/196138.aspx

Thanks.

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

Can you show a piece of code which demonstrates the bug? It sounds
to
me that the socket is maintaining the reference even though the variables
you use are not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
> Hi,
>
> 1. It seems to me that there is a bug when using non-blocking socket
> connect operation, because the LocalEndPoint, RemoteEndPoint of the
> Socket
> are nulls on the client side although that the client and the server
> are
> already connected.
>
> 2. If it is a bug, is there any hotfix for this ?
>
> Thanks.
>
>


Nov 17 '05 #4

P: n/a
Nicholas,

can you give a url where can i find the Product Feedback Center.
i am using .NET 1.1 with visual studio.NET and using c#

Thanks.
"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

I've read the thread, and it appears that MSFT is aware of the bug.
From what I know, there is no hotfix for this yet. It *might* have been
addressed in .NET 2.0, but you need to check the Product Feedback Center for
that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E5**********************************@microsof t.com...
Nicholas,

here is a link that talk on this problem.

http://www.dotnet247.com/247referenc...39/196138.aspx

Thanks.

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

Can you show a piece of code which demonstrates the bug? It sounds
to
me that the socket is maintaining the reference even though the variables
you use are not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
> Hi,
>
> 1. It seems to me that there is a bug when using non-blocking socket
> connect operation, because the LocalEndPoint, RemoteEndPoint of the
> Socket
> are nulls on the client side although that the client and the server
> are
> already connected.
>
> 2. If it is a bug, is there any hotfix for this ?
>
> Thanks.
>
>


Nov 17 '05 #5

P: n/a
Yaron,

The URL for the product feedback center is:

http://lab.msdn.microsoft.com/produc...k/default.aspx

I wouldn't expect a fix for .NET 1.1 though, as they are trying to
address fixes in .NET 2.0.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:43**********************************@microsof t.com...
Nicholas,

can you give a url where can i find the Product Feedback Center.
i am using .NET 1.1 with visual studio.NET and using c#

Thanks.
"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

I've read the thread, and it appears that MSFT is aware of the bug.
From what I know, there is no hotfix for this yet. It *might* have been
addressed in .NET 2.0, but you need to check the Product Feedback Center
for
that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E5**********************************@microsof t.com...
> Nicholas,
>
> here is a link that talk on this problem.
>
> http://www.dotnet247.com/247referenc...39/196138.aspx
>
> Thanks.
>
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Yaron,
>>
>> Can you show a piece of code which demonstrates the bug? It
>> sounds
>> to
>> me that the socket is maintaining the reference even though the
>> variables
>> you use are not.
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mv*@spam.guard.caspershouse.com
>>
>> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> news:E7**********************************@microsof t.com...
>> > Hi,
>> >
>> > 1. It seems to me that there is a bug when using non-blocking
>> > socket
>> > connect operation, because the LocalEndPoint, RemoteEndPoint of the
>> > Socket
>> > are nulls on the client side although that the client and the server
>> > are
>> > already connected.
>> >
>> > 2. If it is a bug, is there any hotfix for this ?
>> >
>> > Thanks.
>> >
>> >
>>
>>
>>


Nov 17 '05 #6

P: n/a
Nicholas,

I think this site is for .NET 2.0, is there a site like this for .NET 1.1 ?

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

The URL for the product feedback center is:

http://lab.msdn.microsoft.com/produc...k/default.aspx

I wouldn't expect a fix for .NET 1.1 though, as they are trying to
address fixes in .NET 2.0.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:43**********************************@microsof t.com...
Nicholas,

can you give a url where can i find the Product Feedback Center.
i am using .NET 1.1 with visual studio.NET and using c#

Thanks.
"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

I've read the thread, and it appears that MSFT is aware of the bug.
From what I know, there is no hotfix for this yet. It *might* have been
addressed in .NET 2.0, but you need to check the Product Feedback Center
for
that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E5**********************************@microsof t.com...
> Nicholas,
>
> here is a link that talk on this problem.
>
> http://www.dotnet247.com/247referenc...39/196138.aspx
>
> Thanks.
>
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Yaron,
>>
>> Can you show a piece of code which demonstrates the bug? It
>> sounds
>> to
>> me that the socket is maintaining the reference even though the
>> variables
>> you use are not.
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mv*@spam.guard.caspershouse.com
>>
>> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> news:E7**********************************@microsof t.com...
>> > Hi,
>> >
>> > 1. It seems to me that there is a bug when using non-blocking
>> > socket
>> > connect operation, because the LocalEndPoint, RemoteEndPoint of the
>> > Socket
>> > are nulls on the client side although that the client and the server
>> > are
>> > already connected.
>> >
>> > 2. If it is a bug, is there any hotfix for this ?
>> >
>> > Thanks.
>> >
>> >
>>
>>
>>


Nov 17 '05 #7

P: n/a
Nicholas,

I think this site is for .NET 2.0, is there a site like this for .NET 1.1 ?

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

The URL for the product feedback center is:

http://lab.msdn.microsoft.com/produc...k/default.aspx

I wouldn't expect a fix for .NET 1.1 though, as they are trying to
address fixes in .NET 2.0.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:43**********************************@microsof t.com...
Nicholas,

can you give a url where can i find the Product Feedback Center.
i am using .NET 1.1 with visual studio.NET and using c#

Thanks.
"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

I've read the thread, and it appears that MSFT is aware of the bug.
From what I know, there is no hotfix for this yet. It *might* have been
addressed in .NET 2.0, but you need to check the Product Feedback Center
for
that.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E5**********************************@microsof t.com...
> Nicholas,
>
> here is a link that talk on this problem.
>
> http://www.dotnet247.com/247referenc...39/196138.aspx
>
> Thanks.
>
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Yaron,
>>
>> Can you show a piece of code which demonstrates the bug? It
>> sounds
>> to
>> me that the socket is maintaining the reference even though the
>> variables
>> you use are not.
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mv*@spam.guard.caspershouse.com
>>
>> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> news:E7**********************************@microsof t.com...
>> > Hi,
>> >
>> > 1. It seems to me that there is a bug when using non-blocking
>> > socket
>> > connect operation, because the LocalEndPoint, RemoteEndPoint of the
>> > Socket
>> > are nulls on the client side although that the client and the server
>> > are
>> > already connected.
>> >
>> > 2. If it is a bug, is there any hotfix for this ?
>> >
>> > Thanks.
>> >
>> >
>>
>>
>>


Nov 17 '05 #8

P: n/a
yaron,

You can try to file an issue to product feedback, but as Nicholas said this
wont help you. I suggest you to contact a support center, they can tell you
wheter a fix is available, if no such fix exists you can ask for a bypass.

http://support.microsoft.com/common/...h=1&gprid=3039

Willy.

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E4**********************************@microsof t.com...
Nicholas,

I think this site is for .NET 2.0, is there a site like this for .NET 1.1
?

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

The URL for the product feedback center is:

http://lab.msdn.microsoft.com/produc...k/default.aspx

I wouldn't expect a fix for .NET 1.1 though, as they are trying to
address fixes in .NET 2.0.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:43**********************************@microsof t.com...
> Nicholas,
>
> can you give a url where can i find the Product Feedback Center.
> i am using .NET 1.1 with visual studio.NET and using c#
>
> Thanks.
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Yaron,
>>
>> I've read the thread, and it appears that MSFT is aware of the
>> bug.
>> From what I know, there is no hotfix for this yet. It *might* have
>> been
>> addressed in .NET 2.0, but you need to check the Product Feedback
>> Center
>> for
>> that.
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mv*@spam.guard.caspershouse.com
>>
>> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> news:E5**********************************@microsof t.com...
>> > Nicholas,
>> >
>> > here is a link that talk on this problem.
>> >
>> > http://www.dotnet247.com/247referenc...39/196138.aspx
>> >
>> > Thanks.
>> >
>> >
>> >
>> > "Nicholas Paldino [.NET/C# MVP]" wrote:
>> >
>> >> Yaron,
>> >>
>> >> Can you show a piece of code which demonstrates the bug? It
>> >> sounds
>> >> to
>> >> me that the socket is maintaining the reference even though the
>> >> variables
>> >> you use are not.
>> >>
>> >>
>> >> --
>> >> - Nicholas Paldino [.NET/C# MVP]
>> >> - mv*@spam.guard.caspershouse.com
>> >>
>> >> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> >> news:E7**********************************@microsof t.com...
>> >> > Hi,
>> >> >
>> >> > 1. It seems to me that there is a bug when using non-blocking
>> >> > socket
>> >> > connect operation, because the LocalEndPoint, RemoteEndPoint of
>> >> > the
>> >> > Socket
>> >> > are nulls on the client side although that the client and the
>> >> > server
>> >> > are
>> >> > already connected.
>> >> >
>> >> > 2. If it is a bug, is there any hotfix for this ?
>> >> >
>> >> > Thanks.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>


Nov 17 '05 #9

P: n/a
yaron,

You can try to file an issue to product feedback, but as Nicholas said this
wont help you. I suggest you to contact a support center, they can tell you
wheter a fix is available, if no such fix exists you can ask for a bypass.

http://support.microsoft.com/common/...h=1&gprid=3039

Willy.

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:E4**********************************@microsof t.com...
Nicholas,

I think this site is for .NET 2.0, is there a site like this for .NET 1.1
?

"Nicholas Paldino [.NET/C# MVP]" wrote:
Yaron,

The URL for the product feedback center is:

http://lab.msdn.microsoft.com/produc...k/default.aspx

I wouldn't expect a fix for .NET 1.1 though, as they are trying to
address fixes in .NET 2.0.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"yaron" <ya***@discussions.microsoft.com> wrote in message
news:43**********************************@microsof t.com...
> Nicholas,
>
> can you give a url where can i find the Product Feedback Center.
> i am using .NET 1.1 with visual studio.NET and using c#
>
> Thanks.
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Yaron,
>>
>> I've read the thread, and it appears that MSFT is aware of the
>> bug.
>> From what I know, there is no hotfix for this yet. It *might* have
>> been
>> addressed in .NET 2.0, but you need to check the Product Feedback
>> Center
>> for
>> that.
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mv*@spam.guard.caspershouse.com
>>
>> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> news:E5**********************************@microsof t.com...
>> > Nicholas,
>> >
>> > here is a link that talk on this problem.
>> >
>> > http://www.dotnet247.com/247referenc...39/196138.aspx
>> >
>> > Thanks.
>> >
>> >
>> >
>> > "Nicholas Paldino [.NET/C# MVP]" wrote:
>> >
>> >> Yaron,
>> >>
>> >> Can you show a piece of code which demonstrates the bug? It
>> >> sounds
>> >> to
>> >> me that the socket is maintaining the reference even though the
>> >> variables
>> >> you use are not.
>> >>
>> >>
>> >> --
>> >> - Nicholas Paldino [.NET/C# MVP]
>> >> - mv*@spam.guard.caspershouse.com
>> >>
>> >> "yaron" <ya***@discussions.microsoft.com> wrote in message
>> >> news:E7**********************************@microsof t.com...
>> >> > Hi,
>> >> >
>> >> > 1. It seems to me that there is a bug when using non-blocking
>> >> > socket
>> >> > connect operation, because the LocalEndPoint, RemoteEndPoint of
>> >> > the
>> >> > Socket
>> >> > are nulls on the client side although that the client and the
>> >> > server
>> >> > are
>> >> > already connected.
>> >> >
>> >> > 2. If it is a bug, is there any hotfix for this ?
>> >> >
>> >> > Thanks.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>


Nov 17 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.