Configure Apache HTTPd with Jakarta Tomcat Connector (mod_jk)
Skip to end of metadata
Go to start of metadata

The communication between the HTTP server and Geronimo can be also done via AJP connectors. By default, both Apache Geronimo distributions (Jetty and Tomcat) have already predefined one AJP13 connector listening on port 8009.

The Jakarta Tomcat Connector mod_jk module is provided as a connector from Apache Tomcat source, Jetty (and obviously Tomcat) is fully compatible with this connector. This module is avaiable when you download the Tomcat source, but also is available for download separately, refer to the following URL for the proper version for your system.

In addition to the mod_jk you will require a file, also available with the Apache Tomcat source distribution. This properties file tells the mod_jk plugin how to connect to the Geronimo server. For a detailed explanation on all the available options for configuring the Jakarta Tomcat Connector visit the following URL:


For practical purposes, the module for Windows and the are included in the Attachments section in this article.

Back to Top

Configure Apache HTTPd

Download the appropriate mod_jk for your platform from the Tomcat web site. For this particular example rename it to and copy it into the <httpd_home>\modules directory. Download and extract the from the Apache Tomcat source (alternatively, download it from the Attachments section) to the <httpd_home>\conf directory.

Edit the httpd.conf file located in the <httpd_home>\conf directory to load the Jakarta Tomcat Connector mod_jk module. Add the following lines at the end of the httpd.conf file.

Excerpt from httpd.conf
LoadModule jk_module modules/			
# Loads the Jakarta Tomcat Connector module

JkWorkersFile <httpd_home>\conf\
# Tells the module the location of the file

JkLogFile     <httpd_home>\logs\mod_jk.log
# Specifies the location for this module's specific log file

JkLogLevel    info
# Sets the module's log level to info

JkMount /console/* ajp13
# Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console.

JkMount will map anything behind /console/ to the worker ajp13. The name ajp13 is defined in the file which is described next. You will need to add more JkMount directives depending on the applications you want to be accessed via the remote HTTPd.


In this example the console has been enabled just for demonstation purposes. In a production environment you will not want to have the console accessible from the other network (normally the Internet). Having the console accessible represents a big security exposure.

The rule is that everything should have restricted access, normally a firewall would be placed in between the HTTP and the application server (depending on the topology) and you should map just the minumum resources necessary to have your application working from the other side.

Back to Top


The, among other things, tells the HTTPd where the Geronimo server is, what version of AJP should use and the port where Geronimo is listening.

Edit the file located in the <httpd_home>\conf directory to match your environment. The following example is an excerpt from the file with just the variables you should focus on.

Minimum requirements for the
# Sets the version of AJP used. The AJP listeners defined in Geronimo are AJP v13.
# Specifies the location of the Geronimo server. Use default localhost for single-tier scenarios. Specify the hostname of the Geronimo server for multi-tier environments.

# Both Tomcat and Jetty come with a predefined AJP13 listener on port 8009

From this example note how the name of the worker is defined, look at the variables definition worker.ajp13.* , ajp13 is the worker name you specified earlier in the httpd.conf.

As a last step, stop and restart the Apache HTTPd to ensure these changes are loaded.

Back to Top


For testing this configuration make sure both Geronimo and HTTPd are up and running.

  1. Check Geronimo connectivity by accessing http://localhost:8080/console , you should see the Geronimo Administration Console.
  2. Check HTTPd connectivity by accessing http://localhost , you should see the Apache HTTPd welcome page.
  3. Check the HTTPd - Geronimo request forwarding by accessing http://localhost/console/ , you shoud be redirected to the Geronimo Administration Console. Note at the end of the URL there is a "/", failing to include this / will result in a Not Found error triggered by the Jakarta Tomcat Connector module.

Back to Top

  • No labels