Iis – Having difficulty connecting IIS to Tomcat

iistomcat

I'm attempting to set IIS up as a 'front end' for Tomcat but have run into a frustrating issue. I can't seem to get the Tomcat connector to recognize when it should be handling the appropriate requests. The isapi_redirect.dll seems to be getting initialized successfully according to the log file, but that's as far as it goes:

[Thu Dec 05 13:00:14.811 2019] [2148:5332] [info] init_jk::jk_isapi_plugin.c (2490): Starting Tomcat/ISAPI/isapi_redirector/1.2.46
[Thu Dec 05 13:00:14.811 2019] [2148:5332] [info] init_jk::jk_isapi_plugin.c (2687): Tomcat/ISAPI/isapi_redirector/1.2.46 initialized

I'm also not seeing this in the IIS log file
GET "/jakarta/isapi_redirect.dll HTTP1.1 which seems to further indicate the redirector doesn't recognize that it should handle the request.

I know Tomcat itself is working because I can browse to 'localhost:8080/examples' which contains some sample Java Servlets to run under Tomcat. However, when I navigate to 'localhost/examples' which should be forwarded from IIS to Tomcat, I get an HTTP 404 error. I've trawled forum post after forum post looking for clues and insights but have come up empty handed so far.

I am currently running Windows Server 2016 on a virtual machine and have IIS 10 and Apache 8.5.49 installed (previously tried Apache 9.0.29). I'm also using version 1.2.46 of the isapi_redirect.dll. I've explicitly followed the how-to guide here: Apache ISAPI connector how-to

I'm beginning to wonder if this issue is related to IIS 10 itself.

Does anyone have any suggestions? If I've omitted any information that would be helpful, please let me know and I can provide it.

Thanks

Best Answer

I seem to have figured this out after a lot of digging in the tomcat log files. Apparently step 6A in the tutorial I linked to above breaks Tomcat. I changed "Connector port=”${port.http}" to "Connector port=”8080" and it started working.

Related Solutions

Tomcat – How to configure uriworkermap.properties in server.xml for Apache – Tomcat integration

Badly Badly misread the title of the question - Long day. The command directive you are looking for is this:

JkMountFile

You would put this directive in your httpd.conf (or a seperate mod_jk.conf depending on how you are setup)

From the documentation for apache

File containing multiple mappings from a context to a Tomcat worker. It is usually called uriworkermap.properties. For inheritance rules, see: JkMountCopy. There is no default value.

I'll leave this here in case anyone is interested.

So, since you have a workers.properties you are probably using mod_jk (which has been depreciated for mod_proxy_ajp*). workers.properties are actually part of the mod_jk configuration.

Yes, the documentation for mod_jk is pretty light. So I'll just go ahead and show you my production configuration as an example - you might have to modify it slightly as we run *nix boxes but the concepts are the same.

You httpd.conf should have something similar to this: This tells apache to include a seperate mod_jk configuration file (you can actually put those directives right in the httpd.conf but... i like modularity). Then configure the alias, and the mount point for your jsp files.
```
Include <path_to_mod_jk.conf>
<VirtualHost *:80>
JkAutoAlias /usr/tomcat/webapps
JkMount /<your_webapp>/*.jsp <your_worker>
```
Your mod_jk.conf should look something like this:

This is where you set all of your generic mod_jk setting for apache, logs, workers file, etc.

    #MOD_JK Config File
    JkWorkersFile <path_to_your_workers.properties>
    JkLogFile /var/log/httpd/mod_jk.log
    JkLogLevel error
    JkShmFile /var/run/mod_jk.shm

3. And finally you should have a workers.properties similar to: Finally we get to the meat of the config. This is where you setup the worker. the options are pretty self explanatory.

    worker.<your_worker_name>.type=ajp13
    worker.list=<your_worker_name>
    #Worker Config
    worker.<your_worker_name>.host=127.0.0.1
    worker.<your_worker_name>.port=8009

And yes, i still run this in production although we are starting a modernization project that will probably see the end of mod_jk and a migration to mod_proxy_ajp

Tomcat – Custom error pages on Apache Tomcat

You have your page paths starting with slashes:

 <error-page>
   <error-code>400</error-code>
   <location>**/error.html**</location>
 </error-page>
 <error-page>
   <error-code>404</error-code>
   <location>**/error.html**</location>
 </error-page>
 <error-page>
   <exception-type>java.lang.Throwable</exception-type>
   <location>**/error.html**</location>
 </error-page>

In this case it might be looking for them in the root of the drive.

If they are in the same folder as web.xml you can try it this way ./error.html

Other than that, I would recommend trying the full path to the file: /var/www/error/error.html or whatever your situation is.

Best Answer

Related Solutions

Tomcat – How to configure uriworkermap.properties in server.xml for Apache – Tomcat integration

Tomcat – Custom error pages on Apache Tomcat

Related Topic