Eliminate timeout when posting reply to a post
-
No problem Steve; just wanted you to know; i bet it has something to do with the high traffic your site gets; i love this site and spend a lot of time on it every day.
Thanks!
Lowell
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible! -
Thanks Steve. Still happens to me. I finally just got in the habbit of doing a copy of my text before I post
-
OK, just got me with the explanation and I forgot the copy/paste.
Doh!
OK, the word from my hot new UK developers with lots of .NET and ASP experience is that it's my fault. They think they've reproduced it a few times in a VM and are fairly confident this is it.
When we went to these ASP.NET forums, we ran into some issues with memory leaks. Actually we didn't know until we had already moved for awhile, but periodically we'd get a "server unavailable" message where all ASP.NET stuff was gone, but the ASP still worked.
So in my very finite web knowledge, I did what any good IIS administrator would do: I set a recycle for the application pool. I set up twice a day, worked great, and life was good.
Well over the years as we've gotten complaints, I had increased that to 6 times a day and as of the server move a few weeks ago it went to every hour. The very talented Stephen D and Steve S at Red Gate (I'm Steve#3), discovered this recycle will lose the session. Which makes the application flip and it doesn't take the post.
So, if you're catching the recycle, whether you've been on the post page for 2 hours or 2 minutes, you lose the text.
They're looking at some Javascript to save to a cookie or something else, but we'd love any suggestions you have.
Saving my text now
-
i think this can be fixed simply by adding some code to either the button that submits the data, or the Sub Page_Load event; the page will have all the values that were submitted, so it would be something like this: i suspect that the submission page either explictly sets the current values to be blank on_load, or simply allows them to be initialized, and they have no value..... by not init-ing them on IsPostBack, the data would remain in place...similar to when you submit username/password, and the password is bad, and you leave the username in place, awaiting a change to the password...
Behind the scenes, an error like invalid viewstate is probably being raised because the session timed out (or the application was restarted...same effect);
simply find the block of code that handles the submit button and in the Try..Catch...don't allow the objects to be initialized, or maybe assign the fields back their value... it's either the submit button or page load events that are wiping the data.
in Page_Load :
If IsPostBack then
'don't init, let the values remain....or assign or ave the values and reassign them? hard to say without the code.
Else
'initing the textboxes to be blank?
End If
Lowell
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible! -
I certainly wouldn't say it's Steve's fault
Clearly these are very busy forums and something is causing a problem over time. For the upcoming revision of SqlServerCentral we will be moving to the latest version of the forum software and will try and prove that this problem is no longer there during testing, or fix it if it is. Lowell - thanks for your suggestion. I think it would be a great fix except for a bit of extra magic that is going on internally to keep the ASP and ASP.NET sides of the site running together. This is effectively converting the POST to a GET so the ultimate destination page has no concept of the previous conversation - it is no longer a postback.
We're looking at a couple of potential fixes/workarounds that should prevent the annoyance of losing your post and we'll keep you posted!
Steven DavidsonDeveloper, Red Gate Software Ltd.
-
Actually it's Andy's fault! He wanted these forums and coded to them
I was happy with plain ol' ASP. Much simpler.
Hopefully this will be fixed when we upgrade.
-
Hey, its better than Snitz - at least the version we had, what a bunch of spaghetti/sql injection waiting to happen! And to be fair, InstantForum is pretty decent software for the price, any wierdness probably not their fault.
Dont get me started on ASP.
Best part about the pending upgrade is I'll finally be able to complain about things needing to be fixed!
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply