项目要提前结项了,明天交货,昨天下午通知我们,今天要加班[emot]unhappy[/emot]
不过还好的是,我的页面没什么BUG
于是一些细节的地方修正完了,老习惯,到博客园逛了一圈,发现一篇有趣的文章:

如果你发现session突然无理由的丢失,而当你认真的检查代码并且排除其它常规可能丢失
的可能性时,你可能会像我一样,几乎要接近崩溃~!
后来发现问题出在我用代码创建一个临时目录然后删除临时目录的删除操作上。
说白了session丢失实质就是:应用程序重起!应用程序什么时候自动重起呢?.................

这个问题一直没碰到,也就没注意过,看了这个文章试了下,果真是这样
作者附上了老外网站关于这个问题解释的原文引用,如下:
请参考:Anand在dotnetindia.com发表的文章

Why ASP.NET Restarts?
Found this link from one of the blogs I was browsing today. This is ASP.NET Forum post by Patrick Y. Ng of MS.

This talks about both 1.0 and 1.1

This behaviour has been bugging lots of people. ASP.Net will restart its application for various reasons. All these reasons are legitimate, but the side effect is that the application will reset all its cache, application state, and InProc session states.
You can detect the restart of application and worker process by using the performance monitor. The counters to monitor are "ASP.NET\Application Restarts" and "ASP.NET\Worker Process Restarts".

For worker process restart, ASP.NET will write an entry in the eventlog to explain why (logLevel in controls how often eventlog is written).

For application restart, however, in v1 and v1.1 there is no easy way for a customer to figure out why a restart happened.

So by listing all reasons for app restart, I hope I can help some customers to understand and avoid the restart.

For v1
------
Things that causes application restart:
- The max compilation limit is reached (look for numRecompilesBeforeApprestart in machine.config)
- Physical application path of the web application has changed.
- Change in global.asax or one of the included files
- Change in machine.config
- Change in web.config in the app root
- Change inside bin directory or its subdirs
- A directory is renamed to bin, or bin is created
- Overwhelming change notifications – too many files are changed too fast in one of content directories – could happen if, for example, files are generated on the fly per request
- Change in the code-access security policy file
- The settings of various attributes in in machine.config affect the restart/shutdown of the worker process itself. However, if you use Windows 2003, and (by default) you are NOT using IIS5 isolation mode, is ignored. Instead, the settings in "Application Pools" in IIS manager is used.

For v1.1
--------
The list for v1.1 is the same as v1, with the following new conditions:
- User code called HttpRuntime.UnloadAppDomain
- Any directory under the web application folder is renamed

IIS 6.0
--------
If you're using IIS 6.0, and you're not using IIS 5 compatible mode, then aspnet_wp.exe will be replaced by w3svc.exe. You may want to go to IIS Manager, go to Application Pools/DefaultAppPool, and see if any of the parameters on the Recycling and Performance tabs are causing the IIS worker process (w3svc.exe) to shutdown.

Back