Search results matching tag 'timeout'

FTP 7.5 SSL disconnects after 15 minutes. Large Files

Comptekcs — Wed, 02 Dec 2009 04:52:58 GMT

I am having the oddest issue so I hope somone has an idea.

Backstory: 3 different ISP's, 2 different physical servers, 1 2008 server and now 2008R2. This is a dedicated FTP server. 2008R2, FTP Role, local firewall off, hardware firewall ports open, and trying to upload anything over about 65MB the connection will reset and start to upload again from 0. On the downloads, same thing but it resumes from where it left off. This issue has happened every time both on 7.0 and 7.5

I have an official SSL cert (not self-signed) using FTPES explicit. Connections/Authentications are good and smaller files upload just fine.

I have adjusted .config files for size limits as some of the forums have suggested but that didn't work.

FileZilla just blips and does the reconnect, no error message. I can't find anything in FTP logs either.

Does anyone have a clue or could point me in where I can get some better logging?

FTP client times out on directory change

computerlady911 — Tue, 27 Oct 2009 19:20:45 GMT

Every time I connect to my ftp server, the connection initially works fine but if I click on any directory the client times out the first time. If I wait until after I get the error, then try again it will work. I am using IIS6 for the ftp and filezilla for the client.

This is how the filezilla reports the command and error.

Command:    CWD /folder name/folder name/Folder Name
Error:    Connection timed out
Error:    Failed to retrieve directory listing

I increased the timeout settings to 1200 sec but no change. Again it does work the second time I try to click on the folder. But this is not a satisfactory result for my users. It happens on every folder.

Re: PHP very slow on IIS7

pierrejoye — Thu, 24 Sep 2009 09:57:33 GMT

I can imagine two possible sources for this problem:

IPv6 is enabled and localhost does not exist or ::1
Mysql's libmysql is used instead of PHP's libmysql.

It happens that the IPv6 problem was the cause for this problem (as you stated later). The 2nd possibility happens a lot when someone installs mysql after PHP, or do a mysql update after having installed PHP.

The latest Mysql's libmysql is not compatible with php's libmysql (and many other, that's not a php specific problem). They suffer from ABI compatibilities issues. The solution is to alter your PATH to be sure that php is first defined( PATH=c:\PHP;c:\mysql for example).

IIS7 SQL Server Connection Pooling Timeout

JAltrichter — Tue, 22 Sep 2009 22:57:11 GMT

I am looking for a little guidance regarding IIS7 SQL Server connection pooling timeout. I have two issues.

As we have migrated our app ASP.NET app to IIS7, I am wondering what a good general value would be for the timeout would be. In IIS6 we would extend the connection timeout to several minutes so that under normal load there would always be a SQL connection available.

Second I am having a mysterious problem setting the connection pool timeout through the ODBC Administrator console. No matter what value I enter, when I re-open the form the value has changed back to the default. This must be something simple, but I am just not seeing it.

Thanks in advance, for any replies.

Jim

Long running ARR requests abort and are not logged

loremipsum123 — Wed, 02 Sep 2009 14:25:43 GMT

Hi -

We're trying to get ARR beta 2 up and running. We have 2 ARR proxy servers routing all requests to 2 IIS servers. If one of the IIS servers takes a long time to serve a page, the ARR server dumps the request somehow and returns this response: "The specified CGI application encountered an error and the server terminated the process." (there's no HTML formatting around it). If I visit the page directly (rather than through ARR), the page serves correctly. I've got a page doing Thread.Sleep to test this behaviour and it's 100% reproducible - it seems to die after 30 seconds.

The server farm's Proxy element has a "Time-out" section that's set to 30 seconds - but changing this doesn't stop the error message.

Nothing gets left in the event log on the ARR boxes, and searching for this message on the net yields no results - so I'm a bit stuck how to troubleshoot!

Any ideas on what might be going wrong, and what I can do to stop it happening? At the very least, how can I return a friendly error page rather than this awful one liner!

Thanks!

dbFullSql timeout issue

Woland — Mon, 24 Aug 2009 22:32:15 GMT

I have a manifest file that needs to run the certain SQL script that sometimes (depending on the server load) will execute longer than 20 seconds. That I believe causes dbFullSql to generate timeout expired exception shown below:

"Error: Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Error count: 1"

I tried passing "connect timeout=380" to the connection string setting but that doesn't seem to have any affect. The solutions I saw online envolved splitting complex SQL into multiple SQL files. In my case it is a simple SQL file that generated the dates table for the reporting purpose and should typically finish in 10 seconds, but due to SQL load, might take longer in certain condition.

Is it possible to encrease the timeout on Sql Provider?

IIS7 -FastCGI -PHP White Screen of Death

gusus — Sat, 07 Mar 2009 04:59:00 GMT

I am having an issue with IIS7 and PHP relating to clients receiving the white screen of death (blank page) after 90 seconds of processing. Standard php processing works fine.

The following are set in php.ini:

max_execution_time = 180
max_input_time = 180
memory_limit = 128M

In the FastCGI configuration on IIS I have the following:

ActivityTimeout 900
IdleTimeout 300
RequestTimeout 500

I have a simple page that runs through loop and sleeps every 15 seconds. If I set the max_execution_time to 30 seconds, I get the php execution time exceeded error as I should with two entries in the page. If I manually set_time_limit(0), it gives the white page of death. I have set php logging and nothing appears in the log. I intentionally put a syntax error to make sure and the syntax error was logged. In addition, I can set the ActivityTimeout to 10 and IIS gives me a 500 error telling me that the FastCGI process exceeded the configuration activity timeout.

The weird thing is the Failed Request Tracking show that the time taken was 30592 msec with a status of 200 (I assume success). However, the last entry in the request trace is "FASTCGI_WAITING_FOR_RESPONSE"...

Any ideas???

Timeout connecting to SharePoint (Internal; works Externally)

dhcrusoe — Fri, 09 Jan 2009 16:18:10 GMT

Hey there,

Here's the situation: We have a MOSS 2007 (SharePoint server) running on IIS 6.x . Connections through our internal network on 10.100.x.x work sometimes, but also timeout after 2-5 seconds, other times. The same goes for its assigned name, http://mokie/ . Connections work intermittantly, but at other times, time out.

External connections, to an IP address that points inbound, work fine - always - and never time out.

What are some things we can check to resolve? Any suggestions?

Thanks!

--Dave

FastCGI Maximum ActivityTimeout

Gengar003 — Mon, 24 Nov 2008 18:14:17 GMT

Hello... on my IIS7 server, I have php implemented via fastCGI.

(Windows Server 2008 build 6001, IIS7 version 7.0.6)

Some of my scripts I need to run for extended periods of time, up to several hours.

While PHP itself has no qualms about this, IIS7's FastCGI "ActivityTimeout" setting refuses to allow itself to be set to more than 3600 seconds (1 hour).

This is inadequate. Using the management console, I cannot set the value to more than 3600, and when I edit the .xml file directly and restart the server, the .xml file is changed to contain 3600, instead of the value I chose.

What can I do to allow a php script to run for more than 3600 seconds (FastCGI's maximum ActivityTimeout)?

A good deal of the script in question's time is spent sleep()ing - is it possible to have FastCGI not count that time toward the activity timeout? Or is there a way to send IIS7 some "activity" from a php script, and thus re-set the timer?

Are there any updates or workarounds that will solve this for me?

Thanks in advance

Re: System.Threading.ThreadAbortException when executing remote web service

lethargicgeek — Wed, 02 Apr 2008 20:16:24 GMT

This may or may not be relevant... but are you modifying any files/directories in your application folder at runtime?

In .Net 2.0 and later, the AppDomain is restarted whenever the file structure is heavily modified. This causes all threads that do not wrap up in a timely fashion to be aborted. Meaning, if your thread is fast enough, it won't be touched. This is different than .net 1.1 where it was only the web.config and bin files that were monitored.

I myself was frustrated in figuring out why I could parse though a 100k file fine but my application threw ThreadAbortExceptions on a 500k file. I killed hours playing with timeouts and configs before finding the solution.

Solution I used to disable File Monitoring:
(requires using System.Reflection)

PropertyInfo p = typeof(System.Web.HttpRuntime).GetProperty("FileChangesMonitor", BindingFlags.NonPublic | BindingFlags.Public | BindingFlags.Static);
object o = p.GetValue(null, null);
FieldInfo f = o.GetType().GetField("_dirMonSubdirs", BindingFlags.Instance | BindingFlags.NonPublic | BindingFlags.IgnoreCase);
object monitor = f.GetValue(o);
MethodInfo m = monitor.GetType().GetMethod("StopMonitoring", BindingFlags.Instance | BindingFlags.NonPublic);
m.Invoke(monitor, new object[] { });

Two good references on the problem:

The formal Complaint:
http://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=240686

Guy Forsyth Discussing the problem
http://weblogs.asp.net/owscott/archive/2006/02/21/ASP.NET-v2.0-_2D00_-AppDomain-recycles_2C00_-more-common-than-before.aspx

Hopes this helps someone...