What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

If you locate my most recent "Quick Answers" result, note it does have a result, but note that it took 104 seconds!

This is much more than the Ajax timeout, but clearly the query didn't stop. This suggests a denial of service attack is possible by requesting a number of very long lasting queries.

The [feature-request] is a better UI when Ajax times out.

The [bug] is the SQL query is not aborted.

(This was promoted from a comment I was going to add here.)

share|improve this question

1 Answer 1

up vote 1 down vote accepted
const int QUERY_TIMEOUT = 120;
command.CommandTimeout = QUERY_TIMEOUT;

It would seem my http request timeout is not inline with my query timeout, besides some browsers hard code timeouts and ignore the web servers. Perhaps I should change it from a sync call to: submit job -> get job id -> poll it. Its a big change though.

EDIT I upped the request timeout to 120 so it should not happen anymore, I hope.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .