 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | trouble load balancing with mod_jk2 | trouble load balancing with mod_jk2 2004-02-02 - By Yiannis Mavroukakis
Back
Not sure about lb, but an shm file of 0000 is bound to get you into trouble
:)
-- --Original Message-- --
From: Aadi Deshpande [mailto:mailinglists@(protected)]
Sent: 02 February 2004 17:18
To: tomcat-user@(protected)
Subject: trouble load balancing with mod_jk2
Greetings,
(Not sure if this is the place for mod_jk2 questions or if there is
another mailing list)
I'm having trouble figuring out how loadbalancing should work using
mod_jk2 with Apache2 and Tomcat 5.0.18.
I have 2 tomcat instances on 2 machines ( running with different port
numbers )
I set them up in a single lb group, using the same lb factor of 80 ( a
number I picked arbitrarily )
my lb configuration is set to graceful=1, stickySession=1, and timeout=0
( i've appended my workers2.properties as additional info ).
However, it seems that when i turn on the apache2 and monitor the
server, all the instances start going to the first instance in the list
and bog that instance down. There doesn't seem to be any load balancing
going on, nor is there any sort of failover when the instance becomes
unusable ( the thread pool hits the maximum of 200 )
The documentation on mod_jk2 isn't all that clear and a lot of it seems
to be geared for implementing the jni mechanism as opposed to the
channel socket ajp mechanism.
I must clearly be doing something wrong, but I can't figure it out.
Additional q's :
the mod_jk2 instance is constantly initing and shutting down. Is this
normal operating procedure?
does a higher lb factor or lower lb factor increase that machine's
chances of being selected?
do dashes ( - ) in the server name have any effect?
I've listed my workers2.properties file inline for review.
Thanks in advance for any help.
Aadi Deshpande
##workers2.properties
[logger]
level=DEBUG
[config:]
file=${serverRoot}/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
size=0000
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
[status:]
info=Status worker, display runtime information
[uri:/jkstatus/*]
info=Display status information and check the config file
group=status:
[lb:lb]
info=Default load balancer.
debug=0
stickySession=1
timeout=0
[channel.socket:tc-server2:6090]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server2:6090
[channel.socket:tc-server2:6190]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server2:6190
[channel.socket:tc-server2:6290]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server2:6290
[channel.socket:tc-server1:6090]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server1:6090
[channel.socket:tc-server1:6190]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server1:6190
[channel.socket:tc-server1:6290]
info=Ajp13 forwarding over socket
graceful=1
debug=0
lb_factor=80
group=lb
tomcatId=tc-server1:6290
[uri:/*.jsp]
info=Map the whole webapp
[uri:/*.sx]
info=Map the whole webapp
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs.
Note:__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ___
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. Jaguar Freight Services and any of its subsidiaries
each reserve the right to monitor all e-mail communications through its
networks.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized
to state them to be the views of any such entity.
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs.
|
|
|
