Need some help with a web/access database

[staffandtra]

I have a password protected section of my web site that contains an Access database, a simple customer list. The problem is it times at at maybe 5 minutes. So if I am typing in data and get side tracked with a phone call, and go back later to complete my entry and save, I am booted out back to the login page.

A) A programmer adjusted the cookies to time out at 12 hours. I cleared the cookies on my machine. I then typed in data, went off to do something else for 20 minutes, then came back to save the data. I was not booted out and the system accepted the save.

B) The next time I went into the database, it went right back to the 5 minute time out.

C) The information below is an email sent to me by this programmer. I am hopeful some of you out there can respond with ideas I can send to him which he can use to maybe fix this problem and eliminate the time out feature, or extend it to at least one hour.

Thanks for your help.

My personal email is david@staffandtrain.com and would appreciate it if you could send your input direct to me.

Best Wishes

Dave Fogg





David,


I have checked everything but the IIS server itself. The request timeout in the web config is set to 90 minutes. The cookies expire after 12 hours. DiscountASP must have a very short IIS timeout to conserve server resources.


The only thing I can think to do now is write a local program that uses an exposed web service to handle the requests and the saves, or change providers, or see if DA will change their settings internally.


Larry

[bruce]

There are other conditions that may trigger a recycle

- Excessive memory usage. If the process uses more than 100MB of memory, IIS will recycle it

- Excessive CPU usage. If the process uses more than 70% CPU cycle within a 5 mintue interval, it will be recycled.

I can't really tell what is the cause. I recommend you open a ticket and have our support staff check why the process is recycled.

Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

[bruce]

i think what you are seeing is process recycling. When the w3wp process recycles, all the memory content is purged (including inproc session)


Our servers are configured to recycle application pool that sits idle for 20 minutes.
Are you using ASP or ASP.NET?

If you are using ASP.NET, you may want to consider using MS SQL session. Afterall, you cannot guarantee that a process will never recycle especially when you are hosted on a shared server.

Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

[staffandtra]

Bruce,

I understand what you wrote about process recycling. And maybe switching to msql could be a solution. However, today I went to my login page, logged in, then went to the database where I clicked Edit to pull up a data field. I typed in a few words, and then minimized the screen to go do something else for about ten minutes. When I went back to the data field I tried to click SAVE and instead of saving the information, I was booted out of that page and taken back to my login page, none of the info I typed was saved.

The reason I point this out is you say the server is set to recycle an application pool that sits idle for 20 minutes. If that were the case, why am I having this problem in as short of a time as ten minutes? Unless I am misunderstanding you, I ought to be able to leave the data field page alone for maybe 18 minutes, then go back and SAVE what I typed as I had not reached the 20 minute mark yet. That is not happening as if I leave the page alone for approximately ten minutes I am still booted out back to the login page.

Do you have any theories on that?

Dave

[jmworr]

Bruce mentioned "When the w3wp process recycles, all the memory content is purged (including inproc session)."

My question is, would using SQLServer mode (instead of inproc) make any difference to the problem described in the post (i.e. being logged out because of process recycling)? I believe the answer is no, but I'm fuzzy on where forms authentication information is stored on the server side?

Mike

[bruce]

I think the login status should be kept in a session variable and using SQL Session should solve this.


Bruce

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)