My .NET 2.0 webservice call only works when Fiddler is running
Hi,
I have a webservice which I deployed to one of servers. The first 2 calls work as they don't bring any data back the next 2 fail on some machines all the time on others randomly UNLESS Fiddler is running !!! The error I am getting is in my other question. I tried using Fiddler to troubleshoot the error but it seems that Fiddler being the the proxy now everything works.
Any advice/help is appreciated
Cheers
H
I have a webservice which I deployed to one of servers. The first 2 calls work as they don't bring any data back the next 2 fail on some machines all the time on others randomly UNLESS Fiddler is running !!! The error I am getting is in my other question. I tried using Fiddler to troubleshoot the error but it seems that Fiddler being the the proxy now everything works.
Any advice/help is appreciated
Cheers
H
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Your question ---------> 1. Running Fiddler on client (That is where I run it), how can that affect the server?
I am not sure how fiddler but I can only assume based on your information. Fiddler might somehow internally handles the errors as it displays the necessary information during web debugging and that is why I inferred that there is no memory leak.
I am not sure how fiddler but I can only assume based on your information. Fiddler might somehow internally handles the errors as it displays the necessary information during web debugging and that is why I inferred that there is no memory leak.
ASKER
Alfred1,
I am not still convinced that a memory leak is involved here. This is my reasoning
1. Nobody runs the app for awhile and I stop and restart my web service in IIS.
2. I run the app on one of my colleague's machines. The first two methods succeed as they only fetch single strings (very small data) the next call to get the larger data fails if user has large data if not it passes.
3. Perform the same steps in 2 above with Filddler running and everything works regardless of size of data
4. The same steps in 2 above are performed on my PC (not running on the IDE bur running the installed app) and everything works, large data or not, Fiddler running or not running!! This is the strange one
I still will not dismiss your suspiscion because this is programming and sometimes what seems impossible just happens.
I am going to move the web service to another server but am short of time at this moment. I have not abandoned the question! Must not take more than a couple of days
Thanks for your assisnatce. Really appreciated
H
I am not still convinced that a memory leak is involved here. This is my reasoning
1. Nobody runs the app for awhile and I stop and restart my web service in IIS.
2. I run the app on one of my colleague's machines. The first two methods succeed as they only fetch single strings (very small data) the next call to get the larger data fails if user has large data if not it passes.
3. Perform the same steps in 2 above with Filddler running and everything works regardless of size of data
4. The same steps in 2 above are performed on my PC (not running on the IDE bur running the installed app) and everything works, large data or not, Fiddler running or not running!! This is the strange one
I still will not dismiss your suspiscion because this is programming and sometimes what seems impossible just happens.
I am going to move the web service to another server but am short of time at this moment. I have not abandoned the question! Must not take more than a couple of days
Thanks for your assisnatce. Really appreciated
H
Just came to my mind while reading your latest post, have you tried using the Web Method attribute, BufferResponse property? You can try setting the BufferResponse property to false since you are dealing with large data. Check the example in the link below for details on how to use BufferResponse property when it is set to false:
http://msdn.microsoft.com/en-us/library/system.web.services.webmethodattribute.bufferresponse%28v=VS.80%29.aspx
http://msdn.microsoft.com/en-us/library/system.web.services.webmethodattribute.bufferresponse%28v=VS.80%29.aspx
ASKER
Yeah will try that tomorrow when I can access my colleague's PC's
Cheers mate
Cheers mate
ASKER