mod_jk2 settings in Apache httpd.conf file

Apache-2.0.43 and mod_jk2-2.0.43 do not use the same worker properties configuration thatmod_jk-2.0.42.

mod_jk2-2.0.43 expects to find a file in the apache/conf directory named "worker2.properties". It is this file that contains the parameters necessary to run mod_jk2-2.0.43 under Apache-2.0.43.

Here is a sample of the file:

[logger]
level=DEBUG

[config:]
#file=${serverRoot}/conf/workers2.properties
#file=c:/Apache2/conf/workers2.properties
file=C:/"Program Files"/"Apache Group"/Apache2/conf/workers2.properties
debug=0
debugEnv=0

[uriMap:]
info=Maps the requests. Options: debug
debug=0

# Alternate file logger
#[logger.file:0]
#level=DEBUG
#file=${serverRoot}/logs/jk2.log

[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess servers
#file=${serverRoot}/logs/jk2.shm
file=C:/"Program Files"/"Apache Group"/Apache2/logs/jk2.shm
size=1000000
debug=0
disabled=0

[workerEnv:]
info=Global server options
timing=1
debug=0
# Default Native Logger (apache2 or win32 )
# can be overriden to a file logger, useful
# when tracing win32 related issues
#logger=logger.file:0

[lb:lb]
info=Default load balancer.
debug=0

#[lb:lb_1]
#info=A second load balancer.
#debug=0

[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=0
tomcatId=localhost:8009

#[channel.socket:localhost:8019]
#info=A second tomcat instance.
#debug=0
#tomcatId=localhost:8019
#lb_factor=1
#group=lb
#group=lb_1
#disabled=0

#[channel.un:/opt/33/work/jk2.socket]
#info=A second channel connecting to localhost:8019 via unix socket
#tomcatId=localhost:8019
#lb_factor=1
#debug=0

[channel.jni:jni]
info=The jni channel, used if tomcat is started inprocess

[status:]
info=Status worker, displays runtime informations

[vm:]
info=Parameters used to load a JVM in the server process
#JVM=C:\Program Files\Java\j2re1.4.0_01\bin\client\jvm.dll (Read from registry)
#OPT=-Djava.class.path=c:/Tomcat/bin/tomcat-jni.jar
OPT=-Djava.class.path=C:/"Program Files"/"Apache Group"/"Tomcat 4.1"/bin/tomcat-jni.jar
OPT=-Dtomcat.home=C:/"Program Files"/"Apache Group"/"Tomcat 4.1"
OPT=-Dcatalina.home=C:/"Program Files"/"Apache Group"/"Tomcat 4.1"
OPT=-Xmx128M
#OPT=-Djava.compiler=NONE
disabled=0

[worker.jni:onStartup]
info=Command to be executed by the VM on startup. This one will start tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=start
disabled=0
stdout=C:/"Program Files"/"Apache Group"/Apache2/logs/stdout.log
stderr=C:/"Program Files"/"Apache Group"/Apache2/logs/stderr.log

[worker.jni:onShutdown]
info=Command to be executed by the VM on shutdown. This one will stop tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=stop
disabled=0

[uri:/jkstatus/*]
info=Display status information and checks the config file for changes.
group=status:

#[uri:127.0.0.1:8003]
#info=Example virtual host. Make sure myVirtualHost is in /etc/hosts to test it
#alias=myVirtualHost:8003

#[uri:127.0.0.1:8003/ex]
#info=Example webapp in the virtual host. It'll go to lb_1 ( i.e. localhost:8019 )
#context=/ex
#group=lb_1

[uri:/examples]
info=Example webapp in the default context.
context=/examples
debug=0

#[uri:/examples1/*]
#info=A second webapp, this time going to the second tomcat only.
#group=lb_1
#debug=0

[uri:/examples/servlets/*]
info=Prefix mapping

[uri:/examples/*.jsp]
info=Extension mapping

[uri:/examples/*]
info=Map the whole webapp

[uri:/examples/servlets/HelloW]
info=Exampel with debug enabled.
debug=10

I hope this helps as I know how frustrating it can be trying to distinguish the differences between the various release of Apache/Tomcat/mod_jk. I'm sure this is documented somewhere but I don't remember where.