Skip to main content

Fixing the Dragnet Timeout

I use SourceGear's Dragnet product for tracking issues and the one thing that's always bothered me is the timeout. So I would modify the timeout in the Web.Config file as well as the IIS but it still never seemed to take it.

Much like Rick Schummer's post about reading magazines for the right tips, subscribing to the SourceGear forums is also a helpful place.

I've linked to the topic but for those who don't want to click, the answer is in the IIS setting "shutdown worker processes after being idle..."

As per users gmagana and kbonnin, In the IIS 6 Admin: Application Pools -> Properties -> Performance -> Shutdown worker processes after being idle for (time in minutes).

So I created a new pool just for the Dragnet app and set it to 720 minutes which should be sufficient so it won't time out.

What's sad is that the original report on this was made in April 2005 and then updated again in September and I've been living with it for months now. Hopefully this post will make it easier for others to find it.


support.sourcegear.com :: View topic - The assault of the Error 500's

Comments

Rick Schummer said…
I really like the SourceGear forum too Andrew. I use SourceOffSite and recently had a problem connecting to my local VSS database. All I had to do is post once and my question was answered by true professionals.
January 19, 2006 at 12:12 PM
Post a Comment

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com
1 comment
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction
12 comments
Read more

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP
7 comments
Read more