Socket.Receive hangs

[Joe Blauth]

Hi all,

I am currently working on a small application that sends messages from a
client to a server and receives messages in return. Basically the
functionality is made with sockets which is working just fine except of one
little thing. whenever the client tries to receive a message the server has
sent it goes into a hang. unfortunately without an error or exception at
all.
the communication itself (sending message from client to server, server
listens on port and receives message, server sends message) is doing its job
so I cannot explain to myself why the socket.receive won't work for the
client (it does on the server side obviously).

but lets dig into some code:

CLIENT
connecting the server:
_Socket = New Socket(AddressF amily.InterNetw ork, SocketType.Stre am,
ProtocolType.Tc p)
Dim oServerIP As System.Net.IPAd dress =
System.Net.IPAd dress.Parse(sSe rverIP)
Dim oRemoteEndPoint As New System.Net.IPEn dPoint(oServerI P, iPort)
_Socket.Connect (oRemoteEndPoin t)

sending message:
Dim oData As Object = sMessage
Dim bytData() As Byte = System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_Socket.Send(by tData)

receiving message:
Dim bytBuffer(1024) As Byte
===Dim iReceived As Integer = _Socket.Receive (bytBuffer)
Dim charChars(iRece ived) As Char
Dim oDecoder As System.Text.Dec oder = System.Text.Enc oding.UTF8.GetD ecoder
Dim iCharLength As Integer = oDecoder.GetCha rs(bytBuffer, 0, iReceived,
charChars, 0)
Dim sData As New String(charChar s)

SERVER
on client connect:
_SocketWorker = _SocketListener .EndAccept(Asyn cResult)
'_SocketListene r is bound to local IP and listens to same port as client

sending message to client:
Dim oData As Object = sMessage
Dim bytData() As Byte = System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_SocketWorker.S end(bytData)

Has anyone an idea why the Socket.Receive on the client side is not doing
the expected job ? it simply runs into a hang and the program itself is not
responding anymore.

thanks a lot for your hints!

Joe.

[Tom Shelton]

On 2008-03-21, Joe Blauth <ca************ *******@web.dew rote:

Hi all,

I am currently working on a small application that sends messages from a
client to a server and receives messages in return. Basically the
functionality is made with sockets which is working just fine except of one
little thing. whenever the client tries to receive a message the server has
sent it goes into a hang. unfortunately without an error or exception at
all.
the communication itself (sending message from client to server, server
listens on port and receives message, server sends message) is doing its job
so I cannot explain to myself why the socket.receive won't work for the
client (it does on the server side obviously).

but lets dig into some code:

CLIENT
connecting the server:
_Socket = New Socket(AddressF amily.InterNetw ork, SocketType.Stre am,
ProtocolType.Tc p)
Dim oServerIP As System.Net.IPAd dress =
System.Net.IPAd dress.Parse(sSe rverIP)
Dim oRemoteEndPoint As New System.Net.IPEn dPoint(oServerI P, iPort)
_Socket.Connect (oRemoteEndPoin t)

sending message:
Dim oData As Object = sMessage
Dim bytData() As Byte = System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_Socket.Send(by tData)

receiving message:
Dim bytBuffer(1024) As Byte
===Dim iReceived As Integer = _Socket.Receive (bytBuffer)
Dim charChars(iRece ived) As Char
Dim oDecoder As System.Text.Dec oder = System.Text.Enc oding.UTF8.GetD ecoder
Dim iCharLength As Integer = oDecoder.GetCha rs(bytBuffer, 0, iReceived,
charChars, 0)
Dim sData As New String(charChar s)

SERVER
on client connect:
_SocketWorker = _SocketListener .EndAccept(Asyn cResult)
'_SocketListene r is bound to local IP and listens to same port as client

sending message to client:
Dim oData As Object = sMessage
Dim bytData() As Byte = System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_SocketWorker.S end(bytData)

Has anyone an idea why the Socket.Receive on the client side is not doing
the expected job ? it simply runs into a hang and the program itself is not
responding anymore.

thanks a lot for your hints!

Joe.

Receive blocks when there is no data available on the socket - so, you
need to ask your self why? Are your client and server on different boxes? Have you
checked to make sure that your app is not being blocked by the windows firewall?
The firewall will allow out going data, but block incomming. There is
another possiblity... A while ago, there was a bug in the framework,
that would cause a hang if the data was aligned on specific size
boundries - and to be honest, I'm not sure if it was fixed, it was a couple
of years ago that I ran into this issue. If it isn't a firewall issue, you might want
to tack a dummy character on the end of your message and see if that fixes the problem.

There are other issues with your code - such as how do you know you have
received the whole transmission? You can't always guarentee that you
will have one receive for every send - in other words, you may have to
do multiple reads to get one send. If your data is small, you may not
ever run into this - but, it is a good idea to think it through now :)

--
Tom Shelton

[Michael D. Ober]

"Tom Shelton" <to*********@YO UKNOWTHEDRILLco mcast.netwrote in message
news:OA******** ******@TK2MSFTN GP04.phx.gbl...

On 2008-03-21, Joe Blauth <ca************ *******@web.dew rote:

>Hi all,

I am currently working on a small application that sends messages from a
client to a server and receives messages in return. Basically the
functionalit y is made with sockets which is working just fine except of
one
little thing. whenever the client tries to receive a message the server
has
sent it goes into a hang. unfortunately without an error or exception at
all.
the communication itself (sending message from client to server, server
listens on port and receives message, server sends message) is doing its
job
so I cannot explain to myself why the socket.receive won't work for the
client (it does on the server side obviously).

but lets dig into some code:

CLIENT
connecting the server:
_Socket = New Socket(AddressF amily.InterNetw ork, SocketType.Stre am,
ProtocolType.T cp)
Dim oServerIP As System.Net.IPAd dress =
System.Net.IPA ddress.Parse(sS erverIP)
Dim oRemoteEndPoint As New System.Net.IPEn dPoint(oServerI P, iPort)
_Socket.Connec t(oRemoteEndPoi nt)

sending message:
Dim oData As Object = sMessage
Dim bytData() As Byte =
System.Text.En coding.ASCII.Ge tBytes(oData.To String)
_Socket.Send(b ytData)

receiving message:
Dim bytBuffer(1024) As Byte
===Dim iReceived As Integer = _Socket.Receive (bytBuffer)
Dim charChars(iRece ived) As Char
Dim oDecoder As System.Text.Dec oder =
System.Text.En coding.UTF8.Get Decoder
Dim iCharLength As Integer = oDecoder.GetCha rs(bytBuffer, 0, iReceived,
charChars, 0)
Dim sData As New String(charChar s)

SERVER
on client connect:
_SocketWorke r = _SocketListener .EndAccept(Asyn cResult)
'_SocketListen er is bound to local IP and listens to same port as client

sending message to client:
Dim oData As Object = sMessage
Dim bytData() As Byte =
System.Text.En coding.ASCII.Ge tBytes(oData.To String)
_SocketWorker. Send(bytData)

Has anyone an idea why the Socket.Receive on the client side is not doing
the expected job ? it simply runs into a hang and the program itself is
not
responding anymore.

thanks a lot for your hints!

Joe.

Receive blocks when there is no data available on the socket - so, you
need to ask your self why? Are your client and server on different boxes?
Have you
checked to make sure that your app is not being blocked by the windows
firewall?
The firewall will allow out going data, but block incomming. There is
another possiblity... A while ago, there was a bug in the framework,
that would cause a hang if the data was aligned on specific size
boundries - and to be honest, I'm not sure if it was fixed, it was a
couple
of years ago that I ran into this issue. If it isn't a firewall issue,
you might want
to tack a dummy character on the end of your message and see if that fixes
the problem.

There are other issues with your code - such as how do you know you have
received the whole transmission? You can't always guarentee that you
will have one receive for every send - in other words, you may have to
do multiple reads to get one send. If your data is small, you may not
ever run into this - but, it is a good idea to think it through now :)

--
Tom Shelton

I believe the bug you are referring to is fixed, at least in dotNet 2.0 and
later. I send/receive variable length packets over TCP all the time with no
problems.

Mike.

[Tom Shelton]

On Mar 22, 9:16*am, "Michael D. Ober" <obermd.@.alum. mit.edu.nospam. >
wrote:

"Tom Shelton" <tom_shel...@YO UKNOWTHEDRILLco mcast.netwrote in message

news:OA******** ******@TK2MSFTN GP04.phx.gbl...

On 2008-03-21, Joe Blauth <catabouche.rem [e-mail] rote:

Hi all,

I am currently working on a small application that sends messages from a
client to a server and receives messages in return. Basically the
functionality is made with sockets which is working just fine except of
one
little thing. whenever the client tries to receive a message the server
has
sent it goes into a hang. unfortunately without an error or exception at
all.
the communication itself (sending message from client to server, server
listens on port and receives message, server sends message) is doing its
job
so I cannot explain to myself why the socket.receive won't work for the
client (it does on the server side obviously).

but lets dig into some code:

CLIENT
connecting the server:
_Socket = New Socket(AddressF amily.InterNetw ork, SocketType.Stre am,
ProtocolType.Tc p)
Dim oServerIP As System.Net.IPAd dress =
System.Net.IPAd dress.Parse(sSe rverIP)
Dim oRemoteEndPoint As New System.Net.IPEn dPoint(oServerI P, iPort)
_Socket.Connect (oRemoteEndPoin t)

sending message:
Dim oData As Object = sMessage
Dim bytData() As Byte =
System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_Socket.Send(by tData)

receiving message:
Dim bytBuffer(1024) As Byte
===Dim iReceived As Integer = _Socket.Receive (bytBuffer)
Dim charChars(iRece ived) As Char
Dim oDecoder As System.Text.Dec oder =
System.Text.Enc oding.UTF8.GetD ecoder
Dim iCharLength As Integer = oDecoder.GetCha rs(bytBuffer, 0, iReceived,
charChars, 0)
Dim sData As New String(charChar s)

SERVER
on client connect:
_SocketWorker = _SocketListener .EndAccept(Asyn cResult)
'_SocketListene r is bound to local IP and listens to same port as client

sending message to client:
Dim oData As Object = sMessage
Dim bytData() As Byte =
System.Text.Enc oding.ASCII.Get Bytes(oData.ToS tring)
_SocketWorker.S end(bytData)

Has anyone an idea why the Socket.Receive on the client side is not doing
the expected job ? it simply runs into a hang and the program itself is
not
responding anymore.

thanks a lot for your hints!

Joe.

Receive blocks when there is no data available on the socket - so, you
need to ask your self why? *Are your client and server on different boxes?
Have you
checked to make sure that your app is not being blocked by the windows
firewall?
The firewall will allow out going data, but block incomming. *There is
another possiblity... *A while ago, there was a bug in the framework,
that would cause a hang if the data was aligned on specific size
boundries - and to be honest, I'm not sure if it was fixed, it was a
couple
of years ago that I ran into this issue. *If it isn't a firewall issue,
you might want
to tack a dummy character on the end of your message and see if that fixes
the problem.

There are other issues with your code - such as how do you know you have
received the whole transmission? *You can't always guarentee that you
will have one receive for every send - in other words, you may have to
do multiple reads to get one send. *If your data is small, you may not
ever run into this - but, it is a good idea to think it through now :)

--
Tom Shelton

I believe the bug you are referring to is fixed, at least in dotNet 2.0 and
later. *I send/receive variable length packets over TCP all the time with no
problems.

Mike.- Hide quoted text -

- Show quoted text -

Probably :) It was a while ago. I can't even remember the size
boundries that caused the issue...

--
Tom Shelton