05:37:23 PM
3ML11RUPH
I think this error occurs if POST data is invalid or the content length for the data sent is incorrect. Basically Web Connection reads the content and forwards it to your Web Connection application, but if the content length is off ReadClient() (which is the ISAPI piece that reads the POST buffer) will fail and thats when you get this error. Could also happen when the POST buffer is too large and the app runs out of memory or some other read related error occurs or when IIS times out the request and basically cuts the client connection off. It should be rare that this happens, but if you can correlate the Request ID with an entry in the log that would be a good start to try and see what's happening. I suspect you'll find that either there's something wrong with the POST data sent or the request is very large that either a timeout or size overload occurs.
I suspect this is a rare error, right?
+++ Rick ---
Hi all!
I've got an app sending 100s of transactions ( records ) per hour from several different machines to a WWWC app. Works great, but ever so often, I get an error message like so:
2012.10.23 15:20:43:969 - n/a - ReadClient Failed on POST data... data was lost. - /rmsdatasync/PublishNewServerTransactions.rms? - 10054 - 17580 - Com:
2012.10.23 15:20:43:969 - 17580_5A2667F91AA4 - Request data conversion failure occurred. Data was lost and the request was cancelled. - /rmsdatasync/PublishNewServerTransactions.rms? - 0 - 17580 - Com: -1:0:0
I assume the hit timed out and simply failed. Is there something I should do about that?
Also, if running two or more instances of a particular app, should each one have it's own temp folder? In my experience, when 2 or more instances of the same app with the same temp path, I sometimes get an error that it couldn't write the wcerrors.txt file ( assuming exact timing of the error output from both instances.)
Thanks in advance for any help.
Gary
West Wind Technologies
Making waves on the Web
from Maui, Hawaii
