I have an asp.net web app using AppFabric for distributed caching. On Application_Start I initialize my connection to AppFabric. This generally takes milliseconds which is perfectly acceptable. On occasion it can take up to 30 se开发者_运维知识库conds to connect.
Prior to a recycle I have a worker process (lets call it wp1). I was under the impression that during a recycle wp1 handled all incoming requests while wp2 was spinning up. I would assume wp2 then becomes responsive when the Application_Start code completes.
Based on my logging, this is not the case. It appears that during a recycle wp2 starts handling requests the moment Application_Start begins and not when it ends. So what do I do to ensure my app doesn't have the 30 second downtime?
cheers in advance
精彩评论