RE: mod_jk.log errors
!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- !-- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ This is what I found in my server.xml, when I comment out the first one my catalina.out looks like the following: Starting service Tomcat-Standalone Apache Tomcat/4.1 Jun 2, 2003 10:38:40 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 So no errors any more but I cannot detect in the log if it is listening, if i issue a netstat -na | grep 8009 I get the result: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN so the port is listened on. So this all looks ok but now I call the index.jsp page in my /navi/ directory it still doesn't work. When I look at my mod_jk.log I got the following errors: [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_ t::map_uri_to_worker [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI ' /navi/index.jsp' [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::ma p_uri_to_worker, done without a match [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_ t::map_uri_to_worker [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI ' /navi/index.jsp' [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::ma p_uri_to_worker, done without a match But I have in my mod_jk.conf (which is included in my httpd.conf) the following: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so /IfModule JkWorkersFile /etc/tomcat4/jk/workers.properties JkLogFile /etc/tomcat4/log/mod_jk.log JkLogLevel debug VirtualHost localhost ServerName localhost JkMount /navi/*.jsp ajp13 In my workers.proerties I have the following entries: # BEGIN workers.properties worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties So what am I missing here ? If you need more information just let me know... Kind regards, Marco Laponder -Oorspronkelijk bericht- Van: John Turner [mailto:[EMAIL PROTECTED] Verzonden: woensdag 28 mei 2003 19:18 Aan: Tomcat Users List Onderwerp: Re: mod_jk.log errors Search in server.xml for '8009' and see how many times it comes up, and whether each occurence is enabled or disabled. John On Wed, 28 May 2003 14:51:38 +0200, Marco Laponder [EMAIL PROTECTED] wrote: It must be in the tomcat4 configuration as when I call netstat -na | grep 8009 I get no output when tomcat is not started, when I start tomcat and call netstat -na | grep 8009 gives the following output: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN So my guess is that somewhere in my configuration of tomcat4 I made a mistake so it is trying to use port 8009 twice. Anyone an idea what I did wrong ? Kind regards, Marco Laponder mlr AT interchain DOT nl Well, the error message is: INFO: Port busy 8009 java.net.BindException: Address already in use That means only one thing: you have something else listening on port 8009. Either another version of Tomcat, or something else. Only you can discover what that is, as none of us have access to your machine. Verify that you have nothing starting up automatically without your knowlege. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - 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]
RE: mod_jk.log errors
Sorry, little bug in my mail ;-) The second connector is not commented out in my current situation ! So my server.xml looks this connector: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ -Oorspronkelijk bericht- Van: Marco Laponder [mailto:[EMAIL PROTECTED] Verzonden: maandag 2 juni 2003 9:42 Aan: 'Tomcat Users List' Onderwerp: RE: mod_jk.log errors !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- !-- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ This is what I found in my server.xml, when I comment out the first one my catalina.out looks like the following: Starting service Tomcat-Standalone Apache Tomcat/4.1 Jun 2, 2003 10:38:40 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 So no errors any more but I cannot detect in the log if it is listening, if i issue a netstat -na | grep 8009 I get the result: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN so the port is listened on. So this all looks ok but now I call the index.jsp page in my /navi/ directory it still doesn't work. When I look at my mod_jk.log I got the following errors: [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_ t::map_uri_to_worker [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI ' /navi/index.jsp' [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::ma p_uri_to_worker, done without a match [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_ t::map_uri_to_worker [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (477)]: Attempting to map URI ' /navi/index.jsp' [Mon Jun 02 10:42:37 2003] [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::ma p_uri_to_worker, done without a match But I have in my mod_jk.conf (which is included in my httpd.conf) the following: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so /IfModule JkWorkersFile /etc/tomcat4/jk/workers.properties JkLogFile /etc/tomcat4/log/mod_jk.log JkLogLevel debug VirtualHost localhost ServerName localhost JkMount /navi/*.jsp ajp13 In my workers.proerties I have the following entries: # BEGIN workers.properties worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties So what am I missing here ? If you need more information just let me know... Kind regards, Marco Laponder -Oorspronkelijk bericht- Van: John Turner [mailto:[EMAIL PROTECTED] Verzonden: woensdag 28 mei 2003 19:18 Aan: Tomcat Users List Onderwerp: Re: mod_jk.log errors Search in server.xml for '8009' and see how many times it comes up, and whether each occurence is enabled or disabled. John On Wed, 28 May 2003 14:51:38 +0200, Marco Laponder [EMAIL PROTECTED] wrote: It must be in the tomcat4 configuration as when I call netstat -na | grep 8009 I get no output when tomcat is not started, when I start tomcat and call netstat -na | grep 8009 gives the following output: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN So my guess is that somewhere in my configuration of tomcat4 I made a mistake so it is trying to use port 8009 twice. Anyone an idea what I did wrong ? Kind regards, Marco Laponder mlr AT interchain DOT nl Well, the error message is: INFO: Port busy 8009 java.net.BindException: Address already in use That means only one thing: you have something else listening on port 8009. Either another version of Tomcat, or something else. Only you can discover what that is, as none of us have access to your machine. Verify that you have nothing starting up automatically without your knowlege. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL
RE: mod_jk.log errors
It must be in the tomcat4 configuration as when I call netstat -na | grep 8009 I get no output when tomcat is not started, when I start tomcat and call netstat -na | grep 8009 gives the following output: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN So my guess is that somewhere in my configuration of tomcat4 I made a mistake so it is trying to use port 8009 twice. Anyone an idea what I did wrong ? Kind regards, Marco Laponder mlr AT interchain DOT nl Well, the error message is: INFO: Port busy 8009 java.net.BindException: Address already in use That means only one thing: you have something else listening on port 8009. Either another version of Tomcat, or something else. Only you can discover what that is, as none of us have access to your machine. Verify that you have nothing starting up automatically without your knowlege. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk.log errors
Search in server.xml for '8009' and see how many times it comes up, and whether each occurence is enabled or disabled. John On Wed, 28 May 2003 14:51:38 +0200, Marco Laponder [EMAIL PROTECTED] wrote: It must be in the tomcat4 configuration as when I call netstat -na | grep 8009 I get no output when tomcat is not started, when I start tomcat and call netstat -na | grep 8009 gives the following output: tcp0 0 0.0.0.0:80090.0.0.0:* LISTEN So my guess is that somewhere in my configuration of tomcat4 I made a mistake so it is trying to use port 8009 twice. Anyone an idea what I did wrong ? Kind regards, Marco Laponder mlr AT interchain DOT nl Well, the error message is: INFO: Port busy 8009 java.net.BindException: Address already in use That means only one thing: you have something else listening on port 8009. Either another version of Tomcat, or something else. Only you can discover what that is, as none of us have access to your machine. Verify that you have nothing starting up automatically without your knowlege. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk.log errors
Yes, Tomcat is running fine when I connect to it on port 8080, I can run the examples and everything runs fine. Also apache is running ok, in fact I had already a running apache and now I want to add java servlets to our application. Thats why I still want to use apache as our webserver, and only do some extra things with tomcat. I removed the jk2.properties, and changed the workers.properties, the catalina.out file now says the following on Tomcat startup: INFO: Starting Coyote HTTP/1.1 on port 8080 May 28, 2003 9:02:02 AM org.apache.jk.common.ChannelSocket init INFO: Port busy 8009 java.net.BindException: Address already in use May 28, 2003 9:02:02 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8010 May 28, 2003 9:02:02 AM org.apache.jk.server.JkMain start INFO: Jk running ID=1 time=5/53 config=null There is still the Address already in use and port 8010, and as you can see jk2.properties is not referenced in the config= clause any more. I searched all the config files mentioned in your HowTo but still cannot figure out why port 8010 is used and why the address already in use message appears. The link between apache and tomcat is not working yet in mod_jk.log still done without a map message. Any more clues for me ? Kind regards, Marco Laponder Your server.xml file looks OK. Does Tomcat work by itself on port 8080? Let's deal with that first. You should be able to independently reach both http://localhost (Apache) and http://locahost:8080 (Tomcat). Remember that you don't need Apache if you don't want it...Tomcat works just fine as an HTTP server on port 80 if you can handle the consequences (running as root on port 80, etc.). Next, delete jk2.properties. You don't need it. Next, change workers.properties. Get rid of all the stuff in there. Workers.properties, to start, just needs this: # BEGIN workers.properties worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties Remember that you don't need JK/JK2 or Apache if you don't want it. Only proceed with configuring JK or JK2 once you can verify that BOTH Apache and Tomcat work fine by themselves. I really suggest looking at my HOWTO, at least for background. It covers everything step by step. http://www.johnturner.com/howto. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk.log errors
Well, the error message is: INFO: Port busy 8009 java.net.BindException: Address already in use That means only one thing: you have something else listening on port 8009. Either another version of Tomcat, or something else. Only you can discover what that is, as none of us have access to your machine. Verify that you have nothing starting up automatically without your knowlege. John On Wed, 28 May 2003 07:58:55 +0200, Marco Laponder [EMAIL PROTECTED] wrote: Yes, Tomcat is running fine when I connect to it on port 8080, I can run the examples and everything runs fine. Also apache is running ok, in fact I had already a running apache and now I want to add java servlets to our application. Thats why I still want to use apache as our webserver, and only do some extra things with tomcat. I removed the jk2.properties, and changed the workers.properties, the catalina.out file now says the following on Tomcat startup: INFO: Starting Coyote HTTP/1.1 on port 8080 May 28, 2003 9:02:02 AM org.apache.jk.common.ChannelSocket init INFO: Port busy 8009 java.net.BindException: Address already in use May 28, 2003 9:02:02 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8010 May 28, 2003 9:02:02 AM org.apache.jk.server.JkMain start INFO: Jk running ID=1 time=5/53 config=null There is still the Address already in use and port 8010, and as you can see jk2.properties is not referenced in the config= clause any more. I searched all the config files mentioned in your HowTo but still cannot figure out why port 8010 is used and why the address already in use message appears. The link between apache and tomcat is not working yet in mod_jk.log still done without a map message. Any more clues for me ? Kind regards, Marco Laponder Your server.xml file looks OK. Does Tomcat work by itself on port 8080? Let's deal with that first. You should be able to independently reach both http://localhost (Apache) and http://locahost:8080 (Tomcat). Remember that you don't need Apache if you don't want it...Tomcat works just fine as an HTTP server on port 80 if you can handle the consequences (running as root on port 80, etc.) . Next, delete jk2.properties. You don't need it. Next, change workers.properties. Get rid of all the stuff in there. Workers.properties, to start, just needs this: # BEGIN workers.properties worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties Remember that you don't need JK/JK2 or Apache if you don't want it. Only proceed with configuring JK or JK2 once you can verify that BOTH Apache and Tomcat work fine by themselves. I really suggest looking at my HOWTO, at least for background. It covers everything step by step. http://www.johnturner.com/howto. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk.log errors
OK, let's take a step back and answer a few questions:
1. what module is being loaded by Apache? This is done using the
LoadModule directive. Is it mod_jk.so, mod_jk2.so, or both?
It is mod_jk.so it is in the mod_jk.conf which is included from the
httpd.conf. The mod_jk.conf was autogenerated initially.
mod_jk.conf:
IfModule !mod_jk.c
LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so
/IfModule
2. what connectors do you have enabled in server.xml? There
are 2 by
default: one on 8080, and one on 8009. There shouldn't be any others
unless you absolutely need them, and in production with
Apache and JK/JK2
you can disable the connector on port 8080.
Hmm, this might be the problem then, I see a lot of connector in the
server.xml file. I pasted the server.xml at the bottom of my message. I
didn't change it much I thought but maybe I messed up somewhere. Is there a
way to recreate the default server.xml file ?
3. how is Apache getting its JK/JK2 configuration? Did you modify
httpd.conf by hand, or are you using some other method?
I auto-generated mod_jk.conf and included that in the httpd.conf file. I use
now a copie of that file so it will not be overwritten by the autogenerate.
4. what .properties files do you have on your system, where
are they, and
what are their contents?
./etc/tomcat4/jk2.properties
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.
## COMMENTS WILL BE _LOST_
## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8019
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
# shm.file=${jkHome}/work/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
I donnot understand why I have this as I think I have jk and not jk2. Not
that I build the mod_jk.so from source as there was no binary for linux
redhat-8.0 available.
./etc/tomcat4/jk/workers.properties
# workers.properties -
#
# This file provides jk derived plugins with the needed information to
# connect to the different tomcat workers. Note that the distributed
# version of this file requires modification before it is usable by a
# plugin.
#
# As a general note, the characters $( and ) are used internally to define
# macros. Do not use them in your own configuration!!!
#
# Whenever you see a set of lines such as:
# x=value
# y=$(x)\something
#
# the final value for y will be value\something
#
# Normaly all you will need to do is un-comment and modify the first three
# properties, i.e. workers.tomcat_home, workers.java_home and ps.
# Most of the configuration is derived from these.
#
# When you are done updating workers.tomcat_home, workers.java_home and ps
# you should have 3 workers configured:
#
# - An ajp12 worker that connects to localhost:8007
# - An ajp13 worker that connects to localhost:8009
# - A jni inprocess worker.
# - A load balancer worker
#
# However by default the plugins will only use the ajp12 worker. To have
# the plugins use other workers you should modify the worker.list property.
#
#
# OPTIONS ( very important for jni mode )
#
# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=/var/tomcat4
#
# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
#
workers.java_home=/usr/java/j2sdk1.4.1_02
#
# You should configure your environment slash... ps=\ on NT and / on UNIX
# and maybe something different elsewhere.
#
ps=/
#
#-- ADVANCED MODE
#-
#
#
#-- DEFAULT worket list --
#-
#
#
# The workers that your plugins should create and work with
#
# Add 'inprocess' if you want JNI connector
worker.list=ajp12, ajp13
# , inprocess
#
#-- DEFAULT ajp12 WORKER DEFINITION --
#-
#
#
# Defining a worker named ajp12 and of type ajp12
# Note that the name and the type do not have to match.
#
worker.ajp12.port=8007
worker.ajp12.host=localhost
worker.ajp12.type=ajp12
#
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
# lbfactor must be 0
# Low lbfactor means less work done by the worker.
worker.ajp12.lbfactor=1
#
Re: mod_jk.log errors
Your server.xml file looks OK.
Does Tomcat work by itself on port 8080? Let's deal with that first. You
should be able to independently reach both http://localhost (Apache) and
http://locahost:8080 (Tomcat). Remember that you don't need Apache if you
don't want it...Tomcat works just fine as an HTTP server on port 80 if you
can handle the consequences (running as root on port 80, etc.).
Next, delete jk2.properties. You don't need it.
Next, change workers.properties. Get rid of all the stuff in there.
Workers.properties, to start, just needs this:
# BEGIN workers.properties
worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
# END workers.properties
Remember that you don't need JK/JK2 or Apache if you don't want it. Only
proceed with configuring JK or JK2 once you can verify that BOTH Apache and
Tomcat work fine by themselves.
I really suggest looking at my HOWTO, at least for background. It covers
everything step by step. http://www.johnturner.com/howto.
John
On Tue, 27 May 2003 17:38:15 +0200, Marco Laponder [EMAIL PROTECTED]
wrote:
OK, let's take a step back and answer a few questions:
1. what module is being loaded by Apache? This is done using the
LoadModule directive. Is it mod_jk.so, mod_jk2.so, or both?
It is mod_jk.so it is in the mod_jk.conf which is included from the
httpd.conf. The mod_jk.conf was autogenerated initially.
mod_jk.conf:
IfModule !mod_jk.c
LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so
/IfModule
2. what connectors do you have enabled in server.xml? There are 2 by
default: one on 8080, and one on 8009. There shouldn't be any others
unless you absolutely need them, and in production with Apache and
JK/JK2 you can disable the connector on port 8080.
Hmm, this might be the problem then, I see a lot of connector in the
server.xml file. I pasted the server.xml at the bottom of my message. I
didn't change it much I thought but maybe I messed up somewhere. Is there
a
way to recreate the default server.xml file ?
3. how is Apache getting its JK/JK2 configuration? Did you modify
httpd.conf by hand, or are you using some other method?
I auto-generated mod_jk.conf and included that in the httpd.conf file. I
use
now a copie of that file so it will not be overwritten by the
autogenerate.
4. what .properties files do you have on your system, where are they,
and what are their contents?
./etc/tomcat4/jk2.properties
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.
## COMMENTS WILL BE _LOST_
## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8019
# Default: # channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
# shm.file=${jkHome}/work/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
I donnot understand why I have this as I think I have jk and not jk2. Not
that I build the mod_jk.so from source as there was no binary for linux
redhat-8.0 available.
./etc/tomcat4/jk/workers.properties
# workers.properties -
#
# This file provides jk derived plugins with the needed information to
# connect to the different tomcat workers. Note that the distributed
# version of this file requires modification before it is usable by a
# plugin.
#
# As a general note, the characters $( and ) are used internally to
define
# macros. Do not use them in your own configuration!!!
#
# Whenever you see a set of lines such as:
# x=value
# y=$(x)\something
#
# the final value for y will be value\something
#
# Normaly all you will need to do is un-comment and modify the first
three
# properties, i.e. workers.tomcat_home, workers.java_home and ps.
# Most of the configuration is derived from these.
#
# When you are done updating workers.tomcat_home, workers.java_home and
ps
# you should have 3 workers configured:
#
# - An ajp12 worker that connects to localhost:8007
# - An ajp13 worker that connects to localhost:8009
# - A jni inprocess worker.
# - A load balancer worker
#
# However by default the plugins will only use the ajp12 worker. To have
# the plugins use other workers you should modify the worker.list
property.
#
#
# OPTIONS ( very important for jni mode )
#
# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
workers.tomcat_home=/var/tomcat4
#
# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
#
workers.java_home=/usr/java/j2sdk1.4.1_02
#
# You should configure
