Am 02.03.2015 um 10:45 schrieb Rajesh Cherukuri:
here is what i can see in modJk log file , we have stopped tomcat 11 a week
back ,
172.xxxxx [27/Feb/2015:*02:28:14* +0000] "GET /xxxxxx/deal-finder
HTTP/1.1"200 15172 20 *lb* tomcat--11** 0 26712 12118 **tomcat-03**
0 820679 4 *20.352845* –
worker configuration
*here is my work.property file*
*worker.lb.common.type=ajp13worker.lb.common.lbfactor=1worker.lb.common.ping_mode=Aworker.lb.common.socket_connect_timeout=10000#
worker.lb.common.connection_pool_size=6worker.lb.common.connection_pool_timeout=600worker.lb.common.socket_keepalive=True*
That is not a production ready config.
- update to the recent version 1.2.40 (if your version is older)
- build your configuration starting from the *source* download linked on
http://tomcat.apache.org/download-connectors.cgi. In the source download
(tarball or zip) there's a conf folder containing a workers.properties
and a httpd-jk.conf file. Look at those and adjust to your environment.
They contain generally useful timeouts etc.
The 20 seconds you are noticing are likely 10 seconds (connect_timeout)
times 2 (retries).
If the server for a Tomcat worker is up and Tomcat itself is down, the
server should typically reject a new connect very fast, because nothing
is listening to the port.
If the server is down it depends on the network situation, whether you
get a fast error (e.g. no route to host etc.) or whether it takes long.
If the server is up and Tomcat is up, but your Tomcat jvm doesn't
respond, it again depends on the details.
If you know, that a node is down, then you should set its activation to
"stopped" to let mod_jk know, that it should no longer try to use it.
You mod_jk log should show more information than what you posted.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
