2008 aio bandwidth blade bladesystem cleaning disposal download DVD edition email Exchange express filter hosting hp IIS IIS7 isapi iscsi KB letogolais linux management microsoft mpio multipath oil oracle performance proliant purification query quota recovery recycler recycling release server solvent speed SQL sqlserver storage system thinner timestamp togo web windows

tomcat connector does not log cs-uri-stem and cs-uri-query properly under IIS7 and windows 2008 web edition longhorn

When installing tomcat to run with IIS 7 on Windows 2008 Longhorn web edition, you need to install ISAPI filter isapi_redirect.dll. This filter internally redirects all request as specified by the worker_file (ie workers.properties) and worker_mount_file (ie uriworkermap.properties) into internal call to the isapi_redirect.dll file in virtual application location specified by extension_uri (for example /jakarta/isapi_redirect.dll). When this redirection happens, on IIS 4 through IIS 6 the values for csUriStem and csUriQuery (in log cs-uri-stem and cs-uri-query) are filled in properly based on actual original request, however on IIS7 running on Windows 2008 you will see cs-uri-stem filled with extension_uri (ie /jakarta/isapi_redirect.dll) and query in cs-uri-query is filled in with minus (-), which signifies no query. This of course is an incorrect behavior and you will lose a lot of quality data from your logs, including the referal pages on initial visits from external links.

This isapi dll tries to update logs by handling SF_NOTIFY_LOG callback from IIS-7 but the log is not reflecting the change request. I have verified that with the source code for isapi_redirector dll located at around line 1440 of jk_isapi_plugin.c source code file.

Scroll down for additional info labeled How to fix the logger issue with jakarta and IIS 7

More info: How to fix the logger issue with jakarta and IIS 7

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

Interestingly enough, this issue was first discovered with IIS 7 and windows Vista. The SP1 for that platform resolves the issue. On Windows 2008 server, this issue has been identified by Microsoft and the qfe team (quality fix engineering) has released an internal hotfix to the customers that request it. If you want the hotfix applied you must contact microsoft support. To help with identification, here is the KB article number 956120. Do not bother looking for it (as of September 2008) as this KB is still unpublished and so is the hotfix. You MUST contact Microsoft support at this time to obtain the hotfix or wait a few months and it should become available via scheduled updates after it goes through more thorough testing cycle.

To reiterate, the problem is not with Tomcat Connector, but with IIS7 handling of SF_NOTIFY_LOG. There is no other quickfix available except for the Microsoft Hotfix.