Application timeout

[neo00]

Hi,
I know that there is a timeout state in web.config file. I want to learn this's timout;

Application["myObject"] = new MyObject();

When myObject will be cleaned? Is there any timeout for application?

Or;

<sessionState timeout="20">

Is session timeout valid for application timeout? If not, can you explain how does application timeout works? How can I set/adjust application timeout?
Thanks.

[srinivas_s]

You will need to set the httpruntime attribute on the server for the applications time out as below , I think executionTimeout is in seconds
<httpRuntime executionTimeout="600">

Following is the msdn link for your reference
http://msdn.microsoft.com/library/de...imesection.asp

sessionTImeout is for the session keys expiry ...

[neo00]

thanks sirinivas_s,
I want to ask that, If I use cache in my web service, is there any dependencies for my cache variable? Such as am I need to set timeout for my web service's cache variable ?

[eideto]

Neo00,

Wanted to straighten out any confusion you might be experiencing.

The Page.Application object actually refers to a global dictionary that isn't collected until the asp.net worker process in recycled or terminated. This is not a very good solution to use for data storage. The executionTimeout attribute on the httpRuntime element in the web.config file will not control what I believe you are referring to. What this setting actually does is establish an arbitrary execution timeout that will halt the execution of the page request if it takes more than the specified time period.

<httpRuntime executionTimeout="600">

Please see this article for good overview of storage options. Should also address your cache questions.

http://www.codeproject.com/aspnet/datastorage.asp

good luck,
eideto

[srinivas_s]

Sorry about my suggestion earlier, When someone posts application timeout in an ASp.net forum my mind goes to the request timing out and thats why i mentioned the http runtime attribute
In addition to what eidito mentioned remember this when using application state

scalability of an application is affected especially if it is used to store shared, updateable state, It is also an unreliable place to store data, because it is replicated with each application instance and is not saved if the application is recycled, it makes more sense to use the data cache in ASP.NET. The most common need for application state is to provide a share point for accessing global, read-only data in an application. By placing global, read-only data in the data cache instead of in application state, you gain all the benefits of cache behavior, with the same ease of access provided by application state. Probably the most compelling advantage of the data cache over application state is memory utilization.(Mentioned because scavenging of data happens in the cache when the memory threshold is reached sometimes..)