2008 480 480Mbps 63 956120 Authorization character connector cs csUriQuery csUriStem debug edition error failed fast fiber filter flashback grafitti hotfix IiiManagerAuth IIS IIS7 image isapi jk_isapi_plugin KB KB956120 log Login microsoft oracle properly QFE query Read server SF_NOTIFY_LOG sophisticated spray Stem street SYSTIMESTAMP timestamp Uri usb user web write

Tomcat connector isapi_redirect.dll does not handle watchdog_interval properly when not initialized or set to zero (off)

I have discovered an issue with isapi_redirect.dll for tomcat connector on IIS. This issue results in watchdog thread performing near tight loop thus degrading performance on server. If debug tracing is enabled, the thread results in approx 1 GB of trace per minute (depending on your server speed). I have notified the developers with solution and they have applied the patch to the main subversion trunk. If you want to take advantage of the fix you will need to recompile your own dll as it is not being released yet.

Summary: watchdog thread starts regardless of the settings on watchdog interval. If setting is zero, the thread loop incessently. If you do not want or cannot recompile from current sources, you can eliminate the near tight loop by changing behavior of your isapi redirect dll. When watchdog interval is set to zero, the clean up happens on each call, otherwise it happens in background. The issue was that clean up was happening on each call and rapidly on background. By setting watchdog_interval to nonzero value, such as 1, you will no longer clean up on each call, rather the cleanup will happen on background every second. It is a good substitute that will eliminate the near tight loop.

More info:

permanent link to article http://freecash.hogger.net/tomcat_connector_isapi_redirect_dll_does_not_handle_watchdog_interval_properly_when_not_initialized_or_set_to_zero_off