Connecting Apache2 with Tomcat5 using mod_jk

royb · 03-07-2004, 02:09 AM

I am having a problem getting apache2 to talk to tomcat5.0.19 using mod_jk.

I have apache2 working properly.

I have tomcat working properly

i have mod_jk compiled and loaded

i have the following connector defined in server.xml
<Connector redirectPort="8443" protocol="AJP/1.3" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" port="8009">
</Connector>

i have following defined in httpd.conf

jkMount /jsp-examples/* ajp13

If i goto url http://abc:8080/jsp-examples i get the examples page

If i go tp url http:/abc/jsp-examples i get internal server error and mod_jk.log shows
[jk_ajp_common.c (955)]: Error connecting to the Tomcat process.
[jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=1
[jk_connect.c (233)]: jk_open_socket, connect() failed errno = 101
[jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 101

i have the workers.properties configured to use port 8009.

Is there something els i need to add to the server.xml file.

Thanks for any help anyone can give.

RoyB

finegan · 03-07-2004, 01:58 PM

Make certain that Tomcat is actually on 8009, I wouldn't imagine that they've changed that, but who knows... I'm only used to Tomcat 4.x and Apache 1.3, but most of the juggling is the same.

What's your workers.properties file look like?

Also, I'll see if we can get this one moved to software, its more fitting there, probably more eyeballs.

Cheers,

Finegan

XavierP · 03-07-2004, 02:10 PM

As above, moving to Software.

royb · 03-07-2004, 03:21 PM

workers.properties is simple

workers list = ajp13

worker.ajp13.type=ajp13
worker.ajp13.port=8009
worker.alp13.host=localhost.

Tomcat is working ok as i can use the applications wwhen specifying the port 8080. But when i try to use the mod_jk connectionm on port 8009 this is where the problem starts. Is there something else required in the tomcat config server.xml to activate the port. It currently only has the one connector entry.

Thanks

finegan · 03-07-2004, 03:41 PM

Nope, 8009 is in there by default unless Tomcat 5.x does something weird, lets make certain 8009 is open, nmap localhost and see what's open, netstat -a will say the same, but nmap will at least tell you if you can get a connection over localhost so if there are some annoying firewall rules in there, it should bring them to light.

Cheers,

Finegan

royb · 03-08-2004, 03:52 AM

I am using suse8.1, nmap not found. Used netsat -a shows *:8009 is LISTEN state.

Tried telnet localhost 8009

received response of connect to address ::1: Connection refused, so i tried telnet 127.0.0.1 8009 and was able to establish connection.

Changed workers.properties so that worker.ajp13.host = 127.0.0.1 and we are away. System seems to be performing normaly.

I do not understand why localhost did not work, but i am happy i have it functioning. Thanks for your help and patience.

RoyB

finegan · 03-09-2004, 06:26 PM

SuSE!!! take a look at /etc/hosts, its got a gooferized version of the localhost naming schema in there, it should look like:

Code:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
66.163.253.201          clockwatching.net melchoir

You'll probably want to change it or non-SuSe prepped apps will barf in the same way, I can't believe I didn't think about that before. Sorry mate.

Cheers,

Finegan