----------------------------------------------------------- New Message on BDOTNET
----------------------------------------------------------- From: BhavtoshS Message 1 in Discussion Hi Group, I have been seeing a significant number of production errors when users attempt to download large files (> 20 MB) in the SPS File Transfer System from an FTP-like custom server. We made a tweak (which I will explain below) to the machine.config, but it caused other issues. The purpose of this email is to ask you for ideas about how to fix this issue. Any help would be greatly appreciated. I won�t confuse the issue by giving too many details about the big picture (unless you really want it). Suffice it to say that the timeout is occurring when our middle-tier component attempts to download a file from the FTP-like server. Due to some out network security restrictions, the middle-tier component must access the FTP server via a Web service, which connects to the FTP server via an FTP library. However, what happens with large files is that the Web service encounters a �deadlock� state (by ASP.NET�s definition) before the entire file has been downloaded, which causes ASP.NET to recycle, which causes timeout, �server application unavailable,� and �underlying connection was closed� errors. I have been able to reproduce this in our development environment. ASP.NET thinks a deadlock state has occurred because it doesn�t see any activity while the FTP library is doing its thing to retrieve the file. But in reality it�s not a deadlock condition. It�s just taking longer than the 3-minute threshold specified in the <processModel> section of the machine.config (responseDeadlockInterval key). We increased this value in machine.config to 8 minutes in production, and it stopped timing out for awhile. But then we started seeing a bunch of other random timeout errors. It appeared these new timeout errors were related to this machine.config change, so we changed it back to 3 minutes, and it seems we are now back at our original condition. I have seen a KB article from Microsoft saying .NET Framework 1.0 SP2 may fix it. I applied this patch in our development environment, but it didn�t help. However, I have installed the Web service on a Win2003/IIS 6.0/.NET 1.1 server, and it seems to work fine. I believe IIS 6.0 and .NET 1.1 are the key, because I tried it on IIS 5.1 and .NET 1.1, but the error still occurs. Upgrading to IIS 6.0 and .NET 1.1 might be an option, but do you have any other ideas on how to make this work without increasing the responseDeadlockInterval value? Any helping hands since im getting off my hands on this problem %$#%$% Bhavtosh ----------------------------------------------------------- To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings. http://groups.msn.com/BDotNet/_emailsettings.msnw Need help? If you've forgotten your password, please go to Passport Member Services. http://groups.msn.com/_passportredir.msnw?ppmprop=help For other questions or feedback, go to our Contact Us page. http://groups.msn.com/contact If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list. mailto:[EMAIL PROTECTED]
