I have an ASP.NET site that is calling a service. It can take the service several minutes to produce the response back in some cases and I am seeing the "Thread was being aborted" exception in those cases.
Is this related to a timeout setting somewhere? Can the timeout be increased?
Update:
Once I have increased the timeout as suggested by Brando Zhang, I am not seeing the "Thread was being aborted" exception, but the page itself is timing out for some reason. By "timing out" I mean that the page is not being refreshed with the contents of the response, once it arrives.
Now my Web.config has the following setting:
<configuration>
<system.web>
<httpRuntime executionTimeout="360" />
</system.web>
</configuration>
Update 2:
Since the original problem outlined in the title is in fact resolved, I feel that the answer provided by Brando Zhang can be accepted as a valid answer to this question.
I will try to resolve the new issue mentioned in the first update by reducing the time it takes for the request to complete or by using long polling.
According to your description, I suggest you could try to increase the executionTimeout property to avoid the thread aborted exception.
Details, you could refer to below config setting:
<configuration> <system.web>
<httpRuntime executionTimeout="360" />
</system.web>
</configuration>
I have a long running report in my app which causes the request to time out, and I want to increase the time limit but I'm not sure where that limit is. I tried setting the command timeout for my DataContext to 99999 seconds but even before that time was up it timed out anyway. I see an executionTimeout="120" set in the web.config but that can't be it because it ran for more than two minutes; I think this setting is ignored in debug mode. There's also this:
<authentication mode="Forms">
<forms loginUrl="~/User/" timeout="720" requireSSL="false" />
</authentication>
But that's only for logging in, right? So how can I tell what timeout setting I need to adjust in order to prevent my report from timing out?
Can you capture the exception in your global.asax and check the stacktrace. This would help you to find the location from where exception is thrown.
I have a one Application in .net ,
I want Auto Logout If data entry Operation rest For Five minute then !
application is auto logout !
will it only logout if nothing is done at screen !
I have tried Below Code But Session Is Expire even if work is on !
<authentication mode="Forms">
<forms loginUrl="../frmLogin.aspx" timeout ="1000" />
</authentication>
<sessionState mode="InProc" timeout="1" cookieless="false">
</sessionState>
Thanks
Regard
Samarth patel
You have to add this in your web.config file for Auto Logout
<system.web>
<sessionState timeout="1" />
</system.web>
You need to set your session timeout to 300seconds. And yes, it will only expire if nothing happens. Even just a request to the server resets it i think. this means that if you have a timed ajax-request in the background that is less than the session timeout, your session will never time out. (I think... :| )
Well, session is defined on the server, in general everytime a user interacts with the server, the session time is lengthened.
So first set your session to 300 seconds.
And perhaps, client side , have a timeout for 3100 ms, that will in the end navigate to the login page. If the user navigates away within the end of the timeout, it's ok, the session is being lengthened.
If he reaches the timeout (and you don't do any ajax stuff!!!), then the server session has ended.
I am running an ASP.NET 2.0 application in IIS 6.0. I want session timeout to be 60 minutes rather than the default 20 minutes. I have done the following
Set <sessionState timeout="60"></sessionState>
in web.config.
Set session timeout to 60 minutes in IIS manager/Web site properties/ASP.NET configuration settings.
Set idle timeout to 60 minutes in application pool properties/performance.
I am still getting a session timeout at 20 minutes. Is there anything else I need to do?
Are you using Forms authentication?
Forms authentication uses it own value for timeout (30 min. by default). A forms authentication timeout will send the user to the login page with the session still active. This may look like the behavior your app gives when session times out making it easy to confuse one with the other.
<system.web>
<authentication mode="Forms">
<forms timeout="50"/>
</authentication>
<sessionState timeout="60" />
</system.web>
Setting the forms timeout to something less than the session timeout can give the user a window in which to log back in without losing any session data.
I don't know about web.config or IIS.
But I believe that from C# code you can do it like
Session.Timeout = 60; // 60 is number of minutes
Use the following code block in your web.config file.
Here default session time out is 80 mins.
<system.web>
<sessionState mode="InProc" cookieless="false" timeout="80" />
</system.web>
Use the following link for Session Timeout with popup alert message.
Session Timeout Example
FYI:The above examples is done with devexpress popup control so you need to customize/replace devexpress popup control with normal popup control. If your using devexpress no need to customize
In my situation, it was Application Pool. It is set to restart when idle for xx mins. When I set it to not restart, it seems to use value from Web Config.
Do you have anything in machine.config that might be taking effect? Setting the session timeout in web.config should override any settings in IIS or machine.config, however, if you have a web.config file somewhere in a subfolder in your application, that setting will override the one in the root of your application.
Also, if I remember correctly, the timeout in IIS only affects .asp pages, not .aspx. Are you sure your session code in web.config is correct? It should look something like:
<sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
stateNetworkTimeout="60"
sqlConnectionString="data source=127.0.0.1;Integrated Security=SSPI"
cookieless="false"
timeout="60"
/>
That is usually all that you need to do...
Are you sure that after 20 minutes, the reason that the session is being lost is from being idle though...
There are many reasons as to why the session might be cleared. You can enable event logging for IIS and can then use the event viewer to see reasons why the session was cleared...you might find that it is for other reasons perhaps?
You can also read the documentation for event messages and the associated table of events.
https://usefulaspandcsharp.wordpress.com/tag/session-timeout/
<authentication mode="Forms">
<forms loginUrl="Login.aspx" name=".ASPXFORMSAUTH" timeout="60" slidingExpiration="true" />
</authentication>
<sessionState mode="InProc" timeout="60" />
If you are using Authentication, I recommend adding the following in web.config file.
In my case, users are redirected to the login page upon timing out:
<authentication mode="Forms">
<forms defaultUrl="Login.aspx" timeout="120"/>
</authentication>
Since ASP.Net core 1.0 (vNext or whatever name is used for it) sessions are implemented differently.
I changed the session timeout value in Startup.cs, void ConfigureServices using:
services.AddSession(options => options.IdleTimeout = TimeSpan.FromSeconds(42));
Or if you want to use the appsettings.json file, you can do something like:
// Appsettings.json
"SessionOptions": {
"IdleTimeout": "00:30:00"
}
// Startup.cs
services.AddSession(options => options.IdleTimeout = TimeSpan.Parse(Config.GetSection("SessionOptions")["IdleTimeout"]));
You can find the setting here in IIS:
It can be found at the server level, web site level, or app level under "ASP".
I think you can set it at the web.config level here. Please confirm this for yourself.
<configuration>
<system.web>
<!-- Session Timeout in Minutes (Also in Global.asax) -->
<sessionState timeout="1440"/>
</system.web>
</configuration>
The default session timeout is defined into IIS to 20 minutes
Follow the procedures below for each site hosted on the IIS 8.5 web
Open the IIS 8.5 Manager.
Click the site name.
Select "Configuration Editor" under the "Management" section.
From the "Section:" drop-down list at the top of the configuration
editor, locate "system.web/sessionState".
Set the "timeout" to "00:20:00 or less”, using the lowest value
possible depending upon the application. Acceptable values are 5
minutes for high-value applications, 10 minutes for medium-value
applications, and 20 minutes for low-value applications.
In the "Actions" pane, click "Apply".
IIS sessions timeout value is for classic .asp applications only, this is controlled on IIS configuration.
In your case For ASP.NET apps, only the web.config-specified timeout value applies.
if you are want session timeout for website than remove
<authentication mode="Forms">
<forms timeout="50"/>
</authentication>
tag from web.config file.
The Timeout property specifies the time-out period assigned to the Session object for the application, in minutes. If the user does not refresh or request a page within the time-out period, the session ends.
IIS 6.0: The minimum allowed value is 1 minute and the maximum is
1440 minutes.
Session.Timeout = 600;
After changing the session timeout value in IIS, Kindly restart the IIS.
To achieve this go to command prompt. Type IISRESET and press enter.
Is there a way to manually increase / decrease the timeout of a specific aspx page?
In the web.config:
<configuration>
<location path="~/Default.aspx">
<system.web>
<httpRuntime executionTimeout="1000"/>
</system.web>
</location>
</configuration>
The one thing to remember with this is that the timeout feature here will only invalidate the Session Timeout, but the user will still remain on whatever page they are on. This may cause issues with the flow of the application. As a rememdy, I keep the following in my Web.config file:
<appSettings>
<!-- Application Timeout is 10 minutes -->
<add key="SessionTimeoutMilliseconds" value="600000"/>
</appSettings>
In addition, my master page has the following code in my code behind file:
' Register Javascript timeout event to redirect to the login page after inactivity
Page.ClientScript.RegisterStartupScript(Me.GetType, "TimeoutScript", _
"setTimeout(""top.location.href = '/EAF/Login.aspx'""," & _
ConfigurationManager.AppSettings("SessionTimeoutMilliseconds") & ");", True)
and you should be all set on both ends.
If you are talking about the amount of time it takes before the page returns a timeout, then mnour's example - you may want to look at the machine.config file as well. If you talking about a session timing out, then you will need to use a JS timer that posts back when it reaches 0.