Rick, Thanks for the response. I added the [shm:] entry to workers2.properties and tried again. The shm.file now gets created, but the redirector is still responding with a 500 to /examples as per the following entry in the PWS log:
17:43:40 192.168.2.54 GET /jakarta/isapi_redirector2.dll 500 In the old jk redirector, there used to be a log_file entry in the 1.0 section of the registry that sent the redirector log to 'iis_redirect.log'. Is there a similar entry for jk2? The IIS HowTo doc doesn't mention such an entry for the 2.0 registry, but does mention a 'logLevel' entry. Is there a way to specify such a log file in the workers2.properties, or maybe the jk2.properties file? As you say, the jk2 documentation is pretty limited and I'm struggling to get it working. Thanks for your help. Mark -----Original Message----- From: Rick Bullotta [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2003 3:04 AM To: 'Tomcat Users List' Subject: RE: Does isapi_redirector2.dll Work With PWS The documentation on what is *really* required to use jk2 is horribly inadequate. You MUST have the [shm:] entry in your workers2.properties for it to work. Here is an example of a "working" one: ===== workers2.properties ===== # Define the communication channel [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 [shm:] file=C:/Program Files/Apache Group/Tomcat 4.1/shm.file size=2000000 # Map the Tomcat uri paths as needed [uri:/examples/*] info=Map the whole webapp [uri:/servlet/*] info=Default invoker =============================== On some specific machines, I've seen a serious error (crash) loading the ISAPI filter (throws a native code exception in MSVCRT/strncmp) when using the 2.0.2 build of jk2, but 2.0.1 worked fine. Yet in some cases, 2.0.2 works OK. Rick Bullotta CTO Lighthammer Software (http://www.lighthammer.com) -----Original Message----- From: Jay Lee [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 9:35 PM To: 'Tomcat Users List' Subject: RE: Does isapi_redirector2.dll Work With PWS 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
