I'm new to the WCF and am having a few problems. NOTE: This post is quite
long as I have included some exceptions and other details relating to my
findings (which are probebly unessersary!).
I have a very simple client - server application using the WCF. There is
one method on the server that accepts an object as an argument. The client
calls this method fairly regularly (lets say every 10 seconds for arguments
sake), sending objects of around 30Kb to the server. The client uses an EDGE
modem to connect to the internet and send these objects. Every now and again
the client seems to 'freeze' or stop transmitting for a few minutes
(sometimes about 10 minutes) and then I get the foloowing exception through
on the client side:
Communications exception thrown whilst trying to write to remote service.
File: C:\Anpr\RemoteQ ueue\0804301056 29.D993BSG.UK.x ml
Exception: System.ServiceM odel.Communicat ionException: An error occurred
while receiving the HTTP response to
http://217.45.150.97:8085/Futronics....ServerService/. This
could be due to the service endpoint binding not using the HTTP protocol.
This could also be due to an HTTP request context being aborted by the server
(possibly due to the service shutting down). See server logs for more
details.
Any ideas what this could be? I'm using BasicHttpBindin g for the client and
server.
What follows is a more detailed look at my findings:
I first thought this problem could be due to lack of signal strength in the
EDGE modem or a loss of connection. However, when this error occurs I can
still use IE and bring up Google etc. I am also aware that at around the
same time I get this error, the CTS line on the modem (Clear To Send line)
starts going up and down - however, this doesn't happen if I were to upload a
large file to an internet site (say 1 meg) which suggests that the size of
the data object has nothing to do with it.
Any help on this matter is appreciated.
James
long as I have included some exceptions and other details relating to my
findings (which are probebly unessersary!).
I have a very simple client - server application using the WCF. There is
one method on the server that accepts an object as an argument. The client
calls this method fairly regularly (lets say every 10 seconds for arguments
sake), sending objects of around 30Kb to the server. The client uses an EDGE
modem to connect to the internet and send these objects. Every now and again
the client seems to 'freeze' or stop transmitting for a few minutes
(sometimes about 10 minutes) and then I get the foloowing exception through
on the client side:
Communications exception thrown whilst trying to write to remote service.
File: C:\Anpr\RemoteQ ueue\0804301056 29.D993BSG.UK.x ml
Exception: System.ServiceM odel.Communicat ionException: An error occurred
while receiving the HTTP response to
http://217.45.150.97:8085/Futronics....ServerService/. This
could be due to the service endpoint binding not using the HTTP protocol.
This could also be due to an HTTP request context being aborted by the server
(possibly due to the service shutting down). See server logs for more
details.
Any ideas what this could be? I'm using BasicHttpBindin g for the client and
server.
What follows is a more detailed look at my findings:
I first thought this problem could be due to lack of signal strength in the
EDGE modem or a loss of connection. However, when this error occurs I can
still use IE and bring up Google etc. I am also aware that at around the
same time I get this error, the CTS line on the modem (Clear To Send line)
starts going up and down - however, this doesn't happen if I were to upload a
large file to an internet site (say 1 meg) which suggests that the size of
the data object has nothing to do with it.
Any help on this matter is appreciated.
James