Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

ASP.Net httpruntime executionTimeout not working (and yes debug=false) -


we noticed executiontimeout has stopped working on our website. working ~last year ... hard when stopped.

we running on:

  • windows-2008x64
  • iis7
  • 32bit binaries
  • managed pipeline mode = classic
  • framework version = v2.0

web.config has

<compilation defaultlanguage="vb" debug="false" batch="true"> <httpruntime executiontimeout="90" /> 

any hints on why seeing timetaken way ~20 minutes. compilation options debugtype (full vs pdbonly) have effect?

datetime timetaken httpmethod status sent received
12/19/10 0:10 901338 post 302 456 24273
12/19/10 0:18 1817446 post 302 0 114236
12/19/10 0:16 246923 post 400 0 28512
12/19/10 0:12 220450 post 302 0 65227
12/19/10 0:22 400150 200 180835 416
12/19/10 0:20 335455 post 400 0 36135
12/19/10 0:57 213210 post 302 0 51558
12/19/10 0:48 352742 post 302 438 25802
12/19/10 0:37 958660 post 400 0 24558
12/19/10 0:06 202025 post 302 0 58349

execution timeout , time-taken time 2 different things. although, size of discrepancy troubling.

time-taken includes of network time in request/response (under conditions.). network transfer time outstrips amount of time request takes. though, normally, i'm used seconds of difference not minutes.

execution timeout refers amount of time worker process spent processing request; subset of time-taken. applies if debug attribute set false; looks have.

of course, assuming first request listed took full 90 seconds of allowed time out, still leaves 13.5 minutes left in time-taken window transfer 24k of data. sounds serious network issue.

so, either have serious transport issue or there web.config file somewhere in tree requests being processed either sets debug true or increases execution timeout astronomical.

another possibility page has either debug attribute set or it's own timeout values.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -