So, what always happens is the same. From the end-user perspective, I get hanging for a few minutes while it's in the process of crashing. Pages don't resolve. Finally when IIS stops my pool, I get 503 errors.
Nothing in Coldfusion-out is strange. Every thing looks normal before the restart.
As stated in my previous discussion on this thread, the event viewer clearly shows the warnings being issued around crash time of the pool doing two things:
1. terminating unexpectedly and then
2. suffereing a fatal communication error with the Windows Process Activiation Service
Finally after it hits the number of allowed errors in the rapid error succession in IIS it errors and the pool is disabled.
Our IT department feels after some research they believe there is a memory leak in the isapi_redirect.dll file. I've read nothing of the sort but that is their response. My isapi log looks as so since we've turned on more detailed logging. Most of the day I have normal : ajp_send_request::jk_ajp_common.c (1658): (cfusion) all endpoints are disconnected, detected by connect check (1), cping (0), send (0) entries.
However right around crash time I get a lot of these over and over again until it crashes:
init_jk::jk_isapi_plugin.c (2779): Initializing shm:(null) errno=-1. Load balancing workers will not function properly.
init_jk::jk_isapi_plugin.c (2813): Jakarta/ISAPI/isapi_redirector/1.2.32 () initialized
init_jk::jk_isapi_plugin.c (2634): Starting Jakarta/ISAPI/isapi_redirector/1.2.32 ()
I don't know what other thing it could be other than the connector as that is the only logs that show what amounts to as errors. While I cannot vouch for all of our code on our server as I didn't write it all, I can say this NEVER happened before CF 10. So I just cannot blame this on bad code or Coldfusion hanging because of malformed code. It just doesn't make sense. This only happened after the switch to CF10.