Session get expired and process terminated .How to manage it

Question

I have to do web base process it takes around 7 to 10 hours to complete

but some times process get terminated when session get expired or

any communication problem

whats the best solution to make it

I have to do on Web

Jean Paul · Answer

Yes Scheduling of Tasks is the right option if the provider supports it.

Suthish Nair · Answer

Why doing this in web site level you can try with SQL Agents jobs etc.. Every hosting server supports scheduling of jobs or tasks..

Jean Paul · Answer

Hello Prabhu Nice to see your reply.. I thought of adding a point too which I missed. In the above case the thread which checks the timeout will also get terminated after 10 minutes and web application get restarted. But the entire process works fine when restarted and the new threads are created. But the restarting causes web application not-responding for a while. The way I implemented was based on cache call back: You can refer it here: http://www.codeproject.com/KB/aspnet/ASPNETService.aspx?msg=3756781#xx3756781xx 1 . On Global.asax a new cache item is created and expires every 9 minutes. On expiry we can call a method as if the user executed a request. 2. On the method call our thread can be created with 9 minutes as execution time range. On time out the threads are terminated. 3. The execution thread reference can be stored in Application object to check whether it is already executing. Hope this will makes more information. Regards Jean Paul

Prabhu Raja · Answer

Hi Paul Your First Option looking Better one. Thanks for it. I will implement this one in my project also.

Jean Paul · Answer

Hello Qasim I had a similar problem of lengthy tasks for my stock market website. I can suggest the solutions which I use there to solve the problems. But certainly they are not the best!! First Option I had a 2 hour task to be performed. My hosting provider used to kill long running threads (> 10minutes) So I broken down the entire 2 hour task to pause and resume service. - The items to be performed are initially created as records in db. - On the application start in Global.asax a thread will be started to perform the activityThread in 9 minutes chunk - Another process will monitor the thread and kills it if > 9 min and create another activityThread immediately So the entire activity will be performed. You can also set a Cache callback mechanism to invoke the service continuously. Second Option Install a windows service or windows application inside the server. Manage the application through ASP.NET to communicate and control. This will run for several hours. Ensure multiple instances are not there. You can start a WCF service through the windows service. Or Run a windows application for each activity in hidden mode. [Server and User Permission issues are the overhead which made me to go for First option] If you get a better solution please let me know. I need to learn it. :)