I've recently upgraded from 6.1.9.1 to 6.7.11.1. I'm now receiving callback terminations, and looking for guidance. Browser is IE 6. Using AjaxPro.dll. Web-server at the moment is my Windows XP Professional box, with me as the only user. However, having the same problems under Windows 2003 when moved into production.
Basically, if my callbacks take longer than 20 seconds or so, I'm still seeing my callback data get returned in Fiddler but the response no longer triggers the callback method anymore. Fiddler shows the following as soon as a response is returned: SESSION STATE: Aborted Request Entity Size: 2358 bytes Response Entity Size: 323 bytes == FLAGS ================== X-HOSTIP: 127.0.0.1 X-TTLB: 13,110 X-CLIENTIP: 127.0.0.1 X-FIDDLER-LIMITATION: Eating a 100 message from the stream. X-CLIENTPORT: 2874 X-TTFB: 16 X-SERVERSOCKET: REUSE I read on another thread about disabling HTTP keep-alives on the webserver but I don't think that will be a possibility given the client environment. Architecturally, the AJAX calls to .NET are, in turn, making back-end calls to ArcIMS (mapping server) on another physical server, and waiting on a response from it before callback. From the response I see in Fiddler, it's clear this is happening, and the bad responses look just like the good ones. Any help appreciated. I can always revert back to 6.1.9.1 as had no problems under that setup. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
