I'm calling a WCF service on my asp.net site. sometimes this service is down and it takes 30seconds to timeout, which slows down my page as I'm calling syncronously. What's the best way around this? decrease timeout? is there a way to see if the service is down before calling?
View 1 RepliesWe have the timeout value set to 120 in our <form> tag within the web.config. We do not have a session timeout set.. and we have various connection strings.
We are having a problem where a session variable will disappear (become NULL) .. but, the form evidently remains 'open'.. or no re-login is required..... so, my question(s):
1. what is the relationship between form timeout and session timeout
2. how do I set session timeout
I have an ASP.NET web application that I can't modify (I only have the binaries). This application connects to a web service and it seems like the connection is closed from the client side (my web app). I have increased the "executionTimeout" in the machine.config of the destination server but my web app seems to still stop after waiting for a while.
Is there a way to increase the timeout time for my web application by simply modifying the web.config? As I said... I can't modify the timeout in the code so my only option would be through config files.
Hopefully I am posting this in the correct forum.
I am having a problem with my ASP.Net Web application. The application is developed using vb.net and is linked to a SQL Server database. Let me explain how the application works and the problem I am experiencing. The system is an online web app which allows registered users to create a CV online. One of the pages within the app gives users the chance to add a cover note to their CV. The page that allows them to do this consists of only a textarea control and a button control. The textarea allows users to input up to 4,000 characters.
Once the user clicks the 'Save' button to save their cover note info, the following code then executes.This code checks to see if the CV already has cover note info, if it does, then the application runs an update statement, otherwise, it runs an insert statement.The table within the database which records the cover note information is called tbl_covernote and has three columns, covernote_id (int and autoincrement), cv_id(int), covernote_text (nvarchar(max)).
The error which occurs sometimes is as follows:
Dim dr As SqlDataReader
Dim param(0) As SqlParameter
Finally [code]...
I have an ASP.Net application that makes an AJAX request to retrieve at report. The report can run for a long time so I set the asyncpostbacktimeout in <asp:ScriptManager /> to 600. However, when I try to run the report, if it runs for longer than 90 seconds it fails to come back. I can see in the IIS logs that the POST request succeeded with a 200 status and I can see the time taken is much less than 600.
The web page dutifully waits for the entire 600 seconds before returning with a timeout error:
Error:
Sys.WebForms.PageRequestManagerTimeoutException:
The server request timed out.
Is there any setting I should be checking in IIS? Connection timeout is 900 seconds.
The session state timeout is set using this web.config element
<sessionState mode="InProc" cookieless="false" timeout="120" />
The forms auth is configured using this web.config element
<system.web>
<authentication mode="Forms">
<forms loginUrl="Login.aspx"
protection="All"
timeout="30"
name=".ASPXAUTH"
path="/"
requireSSL="false"
slidingExpiration="true"
defaultUrl="default.aspx"
cookieless="UseDeviceProfile"
enableCrossAppRedirects="false" />
</authentication>
</system.web>
What is the difference between the timeouts specified in each of these elements? If both are different, how would it work?
I have a page of each every click has ajax call to my server (hence, the ASP extends the session)
I have ASP.NET session set to Xmin. I want when X+1 min expires, I have expiration page. what I did was to set the JS timer to validate every x+1min to see if the session expired (the problem is that the JS and the ASP session timeouts are not synced)
[Code]....
I have an issue to where my users are logged into my system but thier session is null so when they try to do something in the system after 20 minutes, i get null reference expceptions because my session is gon
What is the best practice for handleing the session, should i kick the users out before thier session ends and when they log back in thier session will return or atleast a new one will be created right? How should I handle this?
How to implement timeout in this code:
Response.Write(@"<script language='javascript'>alert('some alert');</script>");
Response.Redirect(Request.ApplicationPath);
I want to show to user message, and after redirect. But in my solution operations occurs very fast, and alert is not shown.
I have a Web app using Forms authentication. I Use Timeout in Web.Config to TimeOut from application that is working fine and I am Redirected to Login page with Message on page "The application timed out. Please ClockIn/Login." When I am Logging again I am Redirected to the same page with same error message and after that if I try Logging again second time I am able to Login.
Following is the code from different form which i am using.
Web.Config
<sessionState timeout="2">
</sessionState>
<authentication mode="Forms">
<forms loginUrl="Login.aspx" protection="All" timeout="2" slidingExpiration="true" defaultUrl="Home.aspx">
</forms>
[Code].....
I'm load testing an asp.net app.The load test is simulating 500 user doing searchs on the site and browsing the results. I'm observing that the more I reduce the session timeout limit (in web.config) the better the page response time.exemple, with a timeout at 10 minutes, I got an average response time of 8.35 seconds.
With a timout at 3 minutes, the average response time for the same page is 3,98 seconds.The session in stored "InProc".
I have a site that when a user logs in it sets their initials into a session variable and sets the timeout value like so:
[Code]....
I want the user to be logged in for 3 hours. This does not work, the session expires after a short period of time, maybe 20 minutes. What do I need to change to make this page level validation work?I have tried setting in web.config also, but this doesn't work either.
<sessionState mode="InProc" cookieless="true" timeout="180" />
We have a asp.net application where users will apply for jobs online. When users fill out the form the page isn't timing out the session. If a user goes back to the main page the last user's information is still available.
I have setup many websites and have never had to make any changes on IIS, under the configuration within the website. The default is 20 minutes we can change it to 8 or 10, but I think this issue should be taken care of in the code. The setting will affect the entire site instead of the pages that need to timeout.
What is the best way to do this within the code?
There is a thread addressing this but it does not provide the type of answer I am seeking.
When login page is requested due to timeout, there is query string parameter "ReturnUrl" which is very nice and I want to keep that. However, timeout is not the only scenario that generates that parameter. If a restricted page is requested before the user is authenticated, such parameter exists too.
Here is my question is, how can the timeout be detected in the code-behind of the login page assuming the login page is directed to by IIS not by code-behind?
I have a button that executes a script using AJAX.Normally when a session is still active the script will return some data that will be placed inside the parent page.If the session expired the AJAX will return the login screen which gets placed inside the parent page which looks really odd.How would I be able to detect a session timeout and do a postback on the parent page?
View 2 Repliesi would like to redirect user to login page after defining session timeout
how to redirect the user to my login.aspx and how to set session time out within web.config
How can I remove or Dispose a session once user navigate from one page to other. I just want to use a session which should expire when user navigate to other page..its same like view state..we don't get viewstate information on page to page. why session: i need to keep one value on page constant on page refresh where as Viewstate will be reset to null on page refresh...and i just don't want to use that session once user navigate to other pages.. where i need to plcae the session dispose in page events or methods?..or is there any way to keep viewstate on page refresh?
View 9 RepliesI have a web page that refreshes every one minute and the solution times out every 20 minutes, would the one minute refresh be considered as user activity and therefore doesn't time out every 20 minutes? And if not, how do I convince the page that the one minute refresh is like a user activity and it shouldn't time out?Here is the javascript to refresh every one minute:
[Code]....
when all were under controll for a long time i suddenly receive today this error in the online page "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. "
View 10 RepliesI want to redirect to login page,when session is timedout. Here is the link i am following [URL] ...
For example: If i am in the page called http://localhost/RealWebApp/Dashboard/RealProfile.aspx
when session is timed out, this page is showing like http://localhost/RealWebApp/Dashboard/logout.aspx
But i wanted to be like : http://localhost/RealWebApp/logout.aspx
If I use like this in master page:
meta.Content = Convert.ToString(Session.Timeout * 60) + ";url=../LogOut.aspx";
then it is redirecting to http://localhost/Logout.aspx
But i wanted to be like : http://localhost/RealWebApp/logout.aspx
How to accomplish this:
protected void Page_Load(object sender, EventArgs e) {
HtmlMeta meta = new HtmlMeta();
meta.HttpEquiv = "Refresh";
meta.Content = Convert.ToString(Session.Timeout * 60) + ";url=LogOut.aspx";
this.Page.Header.Controls.Add(meta);
}
I wanna write a method to get or set session timeout at run time.
View 1 RepliesI'm working with ASP.Net web services and am having a problem with a long-running process that takes about 5 minutes to complete, and it's timing out. To fix this, I was able to set the executionTimeout on the server's web.config to 10 minutes, and then set the .Timeout property on the Web Service object to approximately 9 minutes. Now, I'm worried that this may possibly cause some other web service calls to sit there for 10 minutes before they time out rather than the previous 90-100 seconds. I know the default on the client side is 100 seconds, but wasn't sure if updating the server's timeout setting would affect this.
Bottom line is - Is it safe to update the server's timeout setting to a long amount like 10 minutes, and rely on the default timeout on the client, or could this end up causing some problems?
How to page redirect in Global.asax Session_End ?
View 1 RepliesThe Silverlight app has a link to a different group of reports. This *was* working fine but no more. In the following code you can see the 'Reports' part that it calls another page [URL] namely right here: WHat is happening is when the reports page is called, it goes into 'Session timeout ' right away.
<
StackPanel Orientation="Horizontal"
VerticalAlignment="Top" HorizontalAlignment="Right"
Margin="5, 1">
<HyperlinkButton x:Name
="ReportsLink"
[Code]....
In our application we are using forms authentication, we have given defaulturl also in the config file. But the problem is that it is not getting redirected to the default url when the session timeout is occuring.
View 2 Replies