using the IIS 7 /7.5 tracing Features to locate the mod_jd tomcat ISAPI problem

some day, I get an strange error, “could not get a worker ajp13”, what I did first was to turn on the tracing features of IIS 7.
 

click the Failed Request tracing in the right action panel. here I will log all the request no matter it’s successful or not.

Dump all the details for all the requests.

Then I try the url http://localhost/docs/.

from the dump directly. you can open the xml using the Brower directly.

Click the compact view. the request uri is /docs. at first the ISAP extension module is loaded.

then It get executed. the HTTPExtensionProc method.

that’s it. NO Server side URL rewrite Logic, Like redirect /docs to /jakarta/isapi_redirector.dll

After we added the filters to IIS. and try the trace, we get different Results.

firstly, the rul is still the /docs

the module get loaded also.

this time, the filter get loaded. we should expect a url redirect in server side.

her it is, /docs is redircted to /jakarta/isap_redirector.dll

then the extension get executed.

repeat the logic in the previous config. but this time, it get a lot context

we made it. :)