OK This is a real headrace.
I have an application that makes a web service call. This is a valid web service that pulls some data from SQL Server DB, stacks it into an XML document and returns it to the Winforms app for processing.
It works fine in the debug.
It fails to run normally but returns specific data, indicating that there is no valid record with a fixed ID from DB.
If you switch on Wearhark packet capture, it works fine again once it's released in the release version.
If you start packet capture before reaching that page which requests the service, then these errors are in the same way as when you are running it normally.
The packet capture of one that produces the correct result shows that the application requests and then it receives the expected data.
Errors from one of the packet capture shows that the application requests and then clearly receives "no record returned" error.
One thing we have noted is taking 0.25 / 0.5 seconds to work on working, but when it does not work, it gives very quick response.
Edit: Okay, I knew I forgot something. I was sure, initially, this service was either SQL or so I tested SQL, no problem No debug issues I tapped a test to feed the data in my browser and retrieved a label again. I fed it some data this was good. This service is not service right. Except, apparently, when called through my Winfem app, which confirms the packet capture, sending the correct data and then it only fails under certain conditions Sigh
Does anyone know why this can happen?
This can be an issue with your web method See how it connects / disconnects the database is. See if you can duplicate results without calling the database - you can create results by hand and call the web service apart from this, also prepare a unit test that uses your web method without using the web service call Calls directly and checks its behavior.
Comments
Post a Comment