Hello Atul,

Set the "0" and the session never timeout.
But this perhaps leads you to the problem with your resources.
Each session takes certain amount of system resources and free then when
timeout, and in your case resources never be releases back

---
WBR,  Michael  Nemtsev [.NET/C# MVP].  
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AS> Hi,
AS> How can I avoid application timeout? Generally a web application
AS> time out is
AS> 20 minutes, however, we can define this timeout in web.config to any
AS> number
AS> of minutes. After giving 500 minutes of time out which is about
AS> little more
AS> than 8 hours, the page expires in less than 2 hours. I am confused
AS> here how
AS> to avoid this timeout problem.
AS> I just dont want my page to be expired, should work similar to
AS> windows
AS> application.
AS> Possible?
AS> Regards,
AS> Atu

Take a look at my article on codeproject "Make session last forever"
http://www.codeproject.com/useritems/SessionForever.asp
Hope it's going to help.

George.

there are two timeouts. session timeout and application timeout. if
asp.net is not used for its timeout period, then its shutdown. ou an
bump this up, but recycles ca still happen (say too many inproc sessions).

if you want your page to not timeout, switch to sqlserver session, and
set the session timeout to a couple days (or as long as you want). then
your users will never see lost sessions from recycles. you can even make
the session cookie persistent so that it lasts weeks (handy for a
shopping cart application)

-- bruce (sqlwork.com)