locked
Suggestions to troubleshoot isapi redirector to JBoss RRS feed

  • Question

  • User1422386969 posted

    My ISAPI filter has the "green" arrow, but requests that I have configured to go to Tomcat give a 404 error(request= http://localhost/jmx-console).  The WebServExtension is allowed.  The ajp13 listeners are available on port 8009, and I can get to the jmx-console by going directly to JBOSS(http://localhost:8060/jmx-console).  I just can't seem to get the request forwarded by IIS.  My suspicion is that the worker.properties or uriworkermap.properties is wrong.  Also, the isapi.log is not generated as expected by configuration.  This tells me something is wrong in the IIS setup.  How can I confirm if IIS is trying to forward with out a log.

    # workers.properties

    worker.list=ajp13w

    worker.ajp13w.type=ajp13

    worker.ajp13w.host=localhost

    worker.ajp13w.port=8009

    #uriworkermap.properties 

    /jmx-console/servlet/*=ajp13w

    /jmx-console/*.jsp=ajp13w

    /jmx-console/*=ajp13w

    /jmx-console=ajp13w

    #ISAPI_Redirector.properties

    extension_uri=/jakarta/isapi_redirect.dll

    log_level=debug

    worker_file="C:\jakarta-tomcat\conf\workers.properties"

    worker_mount_file="C:\jakarta-tomcat\conf\uriworkermap.properties"

    Thursday, June 7, 2007 8:11 PM

Answers

  • User-75227868 posted

    I am no expert in tomcat (thats not in the scope of IIS per-se) but I can give you some useful pointers.

    1. The fact that you are getting a 404 error page suggests that IIS is running ok. But bring tomcat (isapi extension) into the picture and there are numerous configurations that can cause the behavior you are seeing. I recommend you double check with this link (http://tomcat.apache.org/connectors-doc/reference/iis.html) and make sure you have correctly configured your tomcat instance. I suspect the issue in somewhere here...

    2. If you still can't get your stuff to work then see what error info is logged in the iis log (%windir%\system32\LogFiles\W3SVC1\) and paste it here. That should somewhat tell us why iis returned a 404.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, June 7, 2007 8:43 PM

All replies

  • User-75227868 posted

    I am no expert in tomcat (thats not in the scope of IIS per-se) but I can give you some useful pointers.

    1. The fact that you are getting a 404 error page suggests that IIS is running ok. But bring tomcat (isapi extension) into the picture and there are numerous configurations that can cause the behavior you are seeing. I recommend you double check with this link (http://tomcat.apache.org/connectors-doc/reference/iis.html) and make sure you have correctly configured your tomcat instance. I suspect the issue in somewhere here...

    2. If you still can't get your stuff to work then see what error info is logged in the iis log (%windir%\system32\LogFiles\W3SVC1\) and paste it here. That should somewhat tell us why iis returned a 404.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, June 7, 2007 8:43 PM
  • User1383173216 posted

    Thank  you Cool for the reference.

     I have been through most of the Jakarta-tomcat site by now without much success.  I am certain that the problem is in the config.  What makes this install not so straightforward is the embeded Tomcat in JBOSS, and my "green-ness" with JBOSS. 

    Any other suggestions would be welcome.

    Here's what the w3svc1 log has:

    #Software: Microsoft Internet Information Services 6.0
    #Version: 1.0
    #Date: 2007-06-11 03:08:57
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
    2007-06-11 03:08:57 127.0.0.1 GET /iisstart.htm - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 200 0 0
    2007-06-11 03:08:57 127.0.0.1 GET /pagerror.gif - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 200 0 0
    2007-06-11 03:09:04 127.0.0.1 GET /jmx-console - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 404 0 2

    Monday, June 11, 2007 12:13 PM
  • User113421904 posted

    Hi,

    (1) Since IIS is running OK to serve other type of contents.

    (2) And you can go directly to JBOSS(http://localhost:8060/jmx-console). 

    It seems the problem is between the IIS and JBoss communication as you mentioned too.

    According to this article:

    The IIS to JBoss connector seems not working correctly. Fortunately there is log available by the AJP13 connector. Can you find it?

     

    Wednesday, June 13, 2007 6:33 AM
  • User-75227868 posted

    The w3svc log says that it encountered error 404.2. It is most likely because you have not enabled the redirector dll in the "web service extension" section. Can you please double check. If you find that your dll is not enabled, please enable and do a iisreset.

    If that does not help, lets first make sure IIS is aware of the redirector dll and is loading it. For that, first lets clear off all IIS activity by doing an iisreset. And now send a request to http://localhost/jmx-console Now run the following command in command prompt: "tlist -m isapi_redirector.dll". If this command returns w3wp.exe as one of the hosts for your dll then IIS is aware of your dll and (most likely) notified it of your new request. And if this is the case then the issue is with the registry-entries\property-files of tomcat and I suggest you take this question to a tomcat discussion forum where you have a better chances of getting this tomcat related question answered.

    If you donot see w3wp.exe in the tlist command output then we can dig more...

    Wednesday, June 13, 2007 5:56 PM