Re: Clients Losing Session
From: bruce barker (nospam_brubar_at_safeco.com)
Date: 12/16/04
- Next message: Juan T. Llibre [MVP]: "Re: Which one to use...."
- Previous message: ronaldlee: "re:Error, Collection is read only"
- In reply to: JIsenstadt: "Clients Losing Session"
- Next in thread: JIsenstadt: "Re: Clients Losing Session"
- Reply: JIsenstadt: "Re: Clients Losing Session"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Dec 2004 13:02:45 -0800
the browser will also timeout. you can not control this. your approach is
wrong. you should start a background thread (probably a pool) to build the
report, then have the page poll for the results.
-- bruce (sqlwork.com)
"JIsenstadt" <JIsenstadt@discussions.microsoft.com> wrote in message
news:9E120FA6-75C6-4F1D-98F3-24F86896F326@microsoft.com...
| I would appreciate it if anybody can help with a issue I am having in an
| ASP.NET application that is timing out before a process has been
completed.
|
| The scenario
| ASP.NET application under IIS 5 runs a crystal report (which has a lot of
| complex formatting) and returns over 6,000 pages. The time to export this
| report to PDF using Crystal Reports Directly on the server is 83 minutes.
| But when the export to PDF is done through the Web Application at exactly
60
| minutes the session terminates. The web application returns the user to
the
| login page (using custom authentication) logged out. In an older version
of
| this web application the same report at exactly 60 minutes returns a "Page
| Not Found" Error or "Server Application Not Available". This version was
not
| using any Authentication. I need to increase the time to about 90 minutes
or
| later so the user will be able to get the completed PDF file.
|
| Details
| IIS has the connection timeout at 900 seconds (or 15 minutes) and ASP.NET
| session timeout to 20 minutes. Both the Web.Config and the Machine.Config
has
| the session timeout at 20 minutes.
| But as I understand this, these values are used only when the session /
| application has been idle for this amount of time. There has to be
another
| setting that controls the amount of time the user can stay logged into a
| given session or the amount of time a user can stay connected to the
server
| (For 60 minutes as demonstrated by the behavior).
| I'm not changing any of the session properties in code.
| There are no error log messages.
| In addition to this when the session terminates for the user. If I
monitor
| the ASP.NET Worker Process thread that is performing the export it
continues
| to run until the export has been completed.
|
|
| Web.Config
| <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424"
| sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
| cookieless="false" timeout="20"/>
|
| Machine.Config
| <processModel enable="true" timeout="Infinite" idleTimeout="Infinite"
| shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000"
| restartQueueLimit="10" memoryLimit="60" webGarden="false"
| cpuMask="0xffffffff" userName="SYSTEM" password="AutoGenerate"
| logLevel="Errors" clientConnectedCheck="0:00:05"
| comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
| responseDeadlockInterval="00:03:00" maxWorkerThreads="20"
maxIoThreads="20"/>
|
| I've looked everywhere I can think of for this timeout configuration. Can
| somebody please help with an idea of where else to look for the timeout
| setting.or what I can do in code to prevent the session from terminating
| before the process has terminated.
| Thank You for your help ahead of time.
|
- Next message: Juan T. Llibre [MVP]: "Re: Which one to use...."
- Previous message: ronaldlee: "re:Error, Collection is read only"
- In reply to: JIsenstadt: "Clients Losing Session"
- Next in thread: JIsenstadt: "Re: Clients Losing Session"
- Reply: JIsenstadt: "Re: Clients Losing Session"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
