Default Timeout for Push Operation

[Matt Hawley]

Hi all,

I'm trying to figure out a problem with the CodePlex installation of Mercurial in which we're trying to push a repository that is about 150MB in size (or larger). We're running in IIS Integrated mode, and have set the max upload size to be about 300MB. However, when trying to push I get the following:

>> hg push -time -debug
using https://localhost:4431/Repo3
sending between command
pushing to https://localhost:4431/Repo3
sending capabilities command
capabilities: unbundle=HG10GZ,HG10BZ,HG10UN branchmap lookup changegroupsubset
sending heads command
searching for changes
common changesets up to 0000000000000
1 changesets found
List of changesets:
<ab71e...>
sending unbundle command
sending 138181097 bytes
abort: error: Connection reset by peer
Time: real 282.927 secs (user 2.761+0.000 sys 13.494+0.000)

I turned on failed request tracing in IIS, and when looking through I see a 2 min 10 sec gap, upon which it returns a message "The I/O operation has been aborted because of either a thread exit or an application request." Looking around, this generally means the client disconnected from the server, and this is the error that IIS reports.

I have the timeouts set in IIS to well exceed this value, so I'm wondering if there's a default timeout that the push operation uses. Any other pointers for figuring out this problem would also be very appreciated.

Thanks,
Matt Hawley
CodePlex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20100222/34d3b6c7/attachment.htm>