I have a mobile application calling a webservice. When I run the application once it works normally, but if i call it again without restarting the application, the webservice is not even triggered.
Do you have an idea of what the problem might be?
views:
32answers:
1
+1
A:
A webservice call is essenially, reading a webpage. So, the real question is -- "Is the GET request coming in?" If so, the problem is with your server; if not, it's with the client.
James Curran
2010-08-24 17:47:31
how i can check this? for the time being, when the webservice is being triggered i am writing the time in a text file. I noted that at the second attempt no time is being written, which means that the webservice is not being triggered.
mouthpiec
2010-08-24 17:53:23
Use Fiddler (www.fiddler2.com) or WireShark (www.wireshark.org) to see the network traffic.
James Curran
2010-08-24 17:56:48
@mouth: Do you have that part of the code wrapped in a try block? Sounds like an exception to me...
Dave Swersky
2010-08-24 17:57:01
@Dave - yes dave .... but it just keeps waiting till a "timeout"
mouthpiec
2010-08-24 17:58:53
@James: a SOAP call is a POST not a GET
John Saunders
2010-08-24 18:01:01
@mouth: If your second network call always fails, something is not being released. Are you closing the network connection after the first successful call?
Dave Swersky
2010-08-24 18:03:39
@Dave: I am using the <webservice>.Dispose() method. Is there any other way to release the network connection?
mouthpiec
2010-08-24 18:11:41
James Curran
2010-08-24 18:19:35
@James: even REST uses more then just the GET request. It's all about HTTP.
John Saunders
2010-08-24 19:32:32