Well here is what works for me (both Tomcat instances are running locally)
[workerEnv]
logger=logger.apache2
sslEnable=0
timing=1
#forwardURICompat
forwardURICompatUnparsed
#forwardURIEscaped
noRecoveryIfRequestSent
noRecoveryIfHeaderSent
disabled=0
debug=5
version=1
# Comment out in production
[logger.apache2]
level=DEBUG
[shm]
file=/var/log/apache2/jk2.shm
size=1048576
disabled=0
debug=5
version=1
[channel.socket:localhost:8009]
#port=8009
#host=localhost
#graceful=1
keepalive=0
timeout=0
ndelay=0
disabled=0
debug=5
version=1
#---LB---
lb_factor=1
[channel.socket:localhost:8019]
#port=8019
#host=localhost
#graceful=1
keepalive=0
timeout=0
ndelay=0
disabled=0
debug=5
version=1
#---LB---
lb_factor=1
#
# Define the workers
#
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
max_connections=0
connectTimeout=0
replyTimeout=0
prepostTimeout=0
disabled=0
debug=5
version=1
#---LB---
level=1
[ajp13:localhost:8019]
channel=channel.socket:localhost:8019
max_connections=0
connectTimeout=0
replyTimeout=0
prepostTimeout=0
disabled=0
debug=5
version=1
#---LB---
level=1
#
# Announce a "status" worker
#
[status:status]
info=Status worker. Displays runtime information.
#
# Set URIs to forward
#
[uri:/jkstatus/*]
group=status:status
[uri:/<path>/*]
group=lb:lb
#---LB---
[lb:lb]
stickySession=0
Stephan Müller wrote:
Sorry, but it has the same effect.
Thanks
Stephan
Try
It has been a while since I touched jk2 but try
group=lb:balanced
PJ
Stephan Müller wrote:
Hallo!
My Enviroment:
Suse Linux 9.1
Tomcat 5.0.28
JK2 Connector 2.0.4
Apache2 2.0.50
I've configured the jk2-connctor to load balance. Here my
worker2.properties:
# Set a Logger
[logger.apache2]
file=/usr/local/apache2/logs/error.log
level=DEBUG
#debug=1
# config settings
[config]
file=/usr/local/apache2/conf/workers2.properties
debug=0
# Shared Memory file settings
[shm]
file=/usr/local/apache2/conf/jk2.shm
size=100000
# communication channel settings for our "HDTTomcat1"
[channel.socket:192.168.120.148:8009]
port=8009
host=192.168.120.148
tomcatId=myTomcat
group=balanced
lb_factor=1
route=jvm1
# communication channel settings for our "HDTTomcat2"
[channel.socket:192.168.120.147:8009]
port=8009
host=192.168.120.147
tomcatId=yourTomcat
group=balanced
lb_factor=1
route=jvm2
# Declare a Tomcat worker
[ajp13:192.168.120.148:8009]
channel=channel.socket:myTomcat
[ajp13:192.168.120.147:8009]
channel=channel.socket:yourTomcat
#Load balanced worker
[lb:balanced]
worker=ajp13:192.168.120.148:8009
worker=ajp13:192.168.120.147:8009
timeout=30
attempts=2
recovery=90
StickySession=1
noWorkersMsg=Server Busy please retry after some time.
noWorkerCodeMsg=503
[uri:/jsp-examples/*]
info= Mapping for examples of tomcat
context=/jsp-examples
group=balanced
[uri:/manager/*]
#uri:/HDTHTTPService/*]
#nfo=HDT MZS.net
[status:]
[uri:/jkstatus/*]
group=status
After start apache2 I'll get these error messages in th error_log of
apache2:
:
:
[Mon Oct 25 16:41:35 2004] [notice] config.update(): done
ajp13:192.168.120.148:8009
[Mon Oct 25 16:41:35 2004] [notice] config.update(): done
ajp13:192.168.120.147:8009
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced timeout 30
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced attempts 2
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced recovery 90
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced stickySession 1
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced noWorkersMsg Server Busy please retry after some time.
[Mon Oct 25 16:41:35 2004] [notice] config.setAttribute() Error setting
lb:balanced noWorkerCodeMsg 503
[Mon Oct 25 16:41:35 2004] [notice] config.update(): done lb:balanced
:
:
Why cannot set apache2 these attributes? What is my mistake? Need I
another
module?
Stephan Müller
---------------------------------------------------------------------
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]
