You can set log level to "debug" instead of "emerg". Someone tried isapi_redirector2.dll and found the setting was at "worker2.properties". If you can not find that setting, try the setting at registery next. This will tell you why it is not working. Green arrow doesn't mean connecting correctly. For instance, if you didn't declare /example mapping to ajp13, you will get a green arrow but it will not connect to /example. However, if you set to "debug", you should read the whole process on "iis_redirect.log" something like that.
Good luck, jay -----Original Message----- From: Mark E. Palandri [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 3:43 PM To: 'Tomcat Users List' Subject: RE: Does isapi_redirector2.dll Work With PWS OK, I found a typo in the 'workersFile' registry entry. I fixed it and restarted PWS. The jakarta ISAPI Filter now has a green up arrow which I assume means that it loaded successfully. But, it still doesn't look like the '/examples' URI is being redirected to Tomcat. I know that something is listening on socket 8009 because if I send it gibberish, I get a nice exception trace log in my Tomcat window indicating as much. If I look in the PWS log, I see the following: 23:34:05 192.168.2.54 GET /jakarta/isapi_redirector2.dll 500 This seems to imply that the redirector intercepted the request and returned a 500 (Internal Server Error). Is there some logging or debug entry that I can set to get the redirector to spit out something more interesting, for example giving a reason for returning the 500? Here is a copy of what my properties files look like jk2.properties -------------- # The default port is 8009 but you can use another one # channelSocket.port=8019 workers2.properties ------------------- # Define the communication channel [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map the Tomcat examples webapp to the Web server uri space [uri:/examples/*] info=Map the whole webapp server.xml ---------- ... <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> ... full copy attached. Thanks, Mark -----Original Message----- From: Mark E. Palandri [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 2:57 PM To: 'Tomcat Users List' Subject: Does isapi_redirector2.dll Work With PWS I am trying to run a vanilla installation of Tomcat 4.1.18 with Microsoft's Personal Web Server (PWS) using the 2.0.2 jk2 redirector (isapi_redirector2.dll) on an NT4 SP6 box. I believe that I've followed all the instructions on how to set this up (jakarta ISAPI filter and 2.0 registry entries), but it is still failing. Given the red down-arrow in the 'ISAPI Filters' tab of the default web site properties, I assume that the DLL failed to load for some reason. Tomcat seems to be running fine, as I can get to the examples servlet using http://localhost:8080/examples. PWS seems to be running fine as I can find the default PWS page at http://localhost/ just fine. Can the jk2 redirector work with PWS or is purely for IIS 5.0? I am using the jk2.properties and workers2.properties files in the "Quick Start JK2 Configuration Guide - Minimum Configuration", as follows: jk2.properties
