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.

Popular posts from this blog

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 distinctions I…

Security in Windows 10

http://www.slate.com/articles/technology/bitwise/2015/08/windows_10_privacy_problems_here_s_how_bad_they_are_and_how_to_plug_them.single.html

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…

AppleSoft

I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…