On 11.12.2009 18:32, gerhardus.geldenh...@gta-travel.com wrote:
Hi
We have upgraded our modjk from .26 to .28
using mod_jk-1.2.28-httpd-2.2.X.so obtained from
http://../tomcat-connectors/jk/binaries/linux/jk-1.2.28/x86_64/
We are running
Server version: Apache/2.2.3
Server built: Nov 12 2008 10:40:14
CentOS release 5.2 (Final)
After upgrading we are seeing random characters in the RR an Cd columns on the
jkserver-status page.
eg
o%2B
o+
����
Upgrade were done by stopping httpd.
Copying new modjk to /etc/httpd/modules/
Editing /etc/httpd/conf.d/modjk.conf to reflect new version.
Requests are being served but the strange characters and there origin a bit
troubling.
Our workers.properties looks as follows:
( There is actually 12 workers but I have removed most to simplify config)
# Worker list
worker.list=xml-gta,jkstatus
# Worker definitions
# main loadbalancer worker
worker.xml-gta.type=lb
worker.xml-gta.max_reply_timeouts=10
#worker.xml-gta.sticky_session=false
worker.xml-gta.retries=6
worker.xml-gta.method=Busyness
worker.xml-gta.balance_workers=worker1, worker2
# status page worker
worker.jkstatus.type=status
# Worker Reference worker.reference.port=8009
worker.reference.type=ajp13
worker.reference.lbfactor=1
worker.reference.socket_timeout=0
worker.reference.socket_keepalive=true
worker.reference.connect_timeout=5000
worker.reference.prepost_timeout=0
worker.reference.reply_timeout=0
worker.reference.retries=6
worker.reference.recovery_options=27
worker.reference.connection_pool_timeout=600
worker.reference.connection_pool_size=2
worker.reference.ping_mode=A
worker.reference.ping_timeout=5000
worker.reference.retry_interval=60
# Balance workers
worker.worker1.reference=worker.reference
worker.worker1.host=10.10.10.10
worker.worker2.reference=worker.reference
worker.worker2.host=10.10.10.11
Regards
It's a known problem. There's an open Bugzilla for that issue. It seems
you need at least around 8 worker for it to happen and I suspect it has
to do with webserver restarts (apachectl graceful or apachectl restart).
Unfortunately I don't yet fully understand the reasons, but noone has
reported an operational problem resulting our of it, like stickyness or
load balancing being broken. Of course we need to fix it ...
Can you confirm it happens only after restarting? And yes, it would be
nice if your could build from the sources yourself and double check the
problem is still there.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
