>>Yes. Since the only recycling option you have set up can't be responsible for the frequent recycling that you are experiencing then I'd suspect a problem such as a memory leak. The IIS log might provide more info on that.
>>
>>Or an alternative approach which gets some internals from HttRuntime in the Application End:
>>http://aspalliance.com/902
>
>Ok, with the details it gives as attached.
>
>a.jpg gives the details of each instance.
>
>b.jpg gives the details of the last instance which was shutdown.
>
>The interesting thing here is that I didn't even send a new compilation. However, IIS reports as if the recompilation limit of 15 has been reached. So, I do not understand that one. How can it be a recompilation if I didn't even send one?

I seem to recall that having debugging enabled can cause this? Check the 'debug' attribute of the compilation tag in web.config.

You can also change the number of recompiles before a recycle - quick search indicates that it's the numRecompilesBeforeApprestart attribute in machine.config. But doing that would really just be avoiding the issue without knowing the cause.....