cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2005/05/15 04:10:12
Modified:jk/native/apache-1.3 mod_jk.c
jk/native/apache-2.0 mod_jk.c
jk/native/common jk_util.c jk_util.h jk_worker.c
jk/native/iis jk_isapi_plugin.c
jk/native/netscape jk_nsapi_plugin.c
jk/xdocs changelog.xml
jk/xdocs/config workers.xml
Log:
Added worker.maintain directive that allows customizing default 10
second maintain timeout.
Revision ChangesPath
1.82 +1 -2 jakarta-tomcat-connectors/jk/native/apache-1.3/mod_jk.c
Index: mod_jk.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-1.3/mod_jk.c,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -r1.81 -r1.82
--- mod_jk.c 14 May 2005 10:08:23 - 1.81
+++ mod_jk.c 15 May 2005 11:10:11 - 1.82
@@ -1738,7 +1738,6 @@
private_data.read_body_started = JK_FALSE;
private_data.r = r;
-/* TODO: Make maintain call configurable */
wc_maintain(l);
jk_init_ws_service(s);
1.145 +1 -2 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c
Index: mod_jk.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -r1.144 -r1.145
--- mod_jk.c 14 May 2005 10:08:23 - 1.144
+++ mod_jk.c 15 May 2005 11:10:11 - 1.145
@@ -1868,7 +1868,6 @@
private_data.read_body_started = JK_FALSE;
private_data.r = r;
-/* TODO: Make maintain call configurable */
wc_maintain(xconf-log);
jk_init_ws_service(s);
1.68 +10 -2 jakarta-tomcat-connectors/jk/native/common/jk_util.c
Index: jk_util.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_util.c,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- jk_util.c 5 May 2005 17:52:27 - 1.67
+++ jk_util.c 15 May 2005 11:10:11 - 1.68
@@ -76,7 +76,9 @@
#define RETRIES_OF_WORKER (retries)
#define DEFAULT_WORKER JK_AJP13_WORKER_NAME
-#define WORKER_LIST_PROPERTY_NAME (worker.list)
+#define WORKER_LIST_PROPERTY_NAME (worker.list)
+#define WORKER_MAINTAIN_PROPERTY_NAME (worker.maintain)
+#define DEFAULT_MAINTAIN_TIME (60)
#define DEFAULT_LB_FACTOR (1)
#define LOG_FORMAT (log_format)
@@ -822,6 +824,12 @@
return JK_FALSE;
}
+int jk_get_worker_maintain_time(jk_map_t *m)
+{
+return jk_map_get_int(m, WORKER_MAINTAIN_PROPERTY_NAME,
+ DEFAULT_MAINTAIN_TIME);
+}
+
int jk_get_worker_mx(jk_map_t *m, const char *wname, unsigned *mx)
{
char buf[1024];
1.33 +2 -1 jakarta-tomcat-connectors/jk/native/common/jk_util.h
Index: jk_util.h
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_util.h,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- jk_util.h 26 Apr 2005 15:28:18 - 1.32
+++ jk_util.h 15 May 2005 11:10:11 - 1.33
@@ -147,6 +147,7 @@
int jk_get_worker_def_cache_size(int protocol);
+int jk_get_worker_maintain_time(jk_map_t *m);
#define TC32_BRIDGE_TYPE32
#define TC33_BRIDGE_TYPE33
1.33 +6 -6 jakarta-tomcat-connectors/jk/native/common/jk_worker.c
Index: jk_worker.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_worker.c,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- jk_worker.c 24 Apr 2005 09:54:47 - 1.32
+++ jk_worker.c 15 May 2005 11:10:11 - 1.33
@@ -38,6 +38,7 @@
/* Global worker list */
static jk_map_t *worker_map;
static JK_CRIT_SEC worker_lock;
+static int worker_maintain_time = 0;
int wc_open(jk_map_t *init_data, jk_worker_env_t *we, jk_logger_t *l)
{
@@ -65,6 +66,8 @@
return JK_FALSE;
}
+worker_maintain_time = jk_get_worker_maintain_time(init_data);
+
if (!build_worker_map(init_data, we-worker_list,
we-num_of_workers, we, l)) {
close_workers(l);
@@ -279,15 +282,12 @@
JK_TRACE_ENTER(l);
-/* TODO: make maintatin time configurable
- * For now use 10 seconds.
- */
-if (sz 0) {
+if (sz 0 worker_maintain_time 0) {
int i;
time_t now;
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
pero2005/05/05 08:59:10 Modified:jk/xdocs changelog.xml jk/xdocs/config workers.xml Log: Add doc of my stopped change and the very fine new secret default lb worker attribute - thanks mladen. Revision ChangesPath 1.28 +13 -0 jakarta-tomcat-connectors/jk/xdocs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/changelog.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- changelog.xml 29 Apr 2005 20:08:53 - 1.27 +++ changelog.xml 5 May 2005 15:59:10 - 1.28 @@ -21,6 +21,19 @@ new documentation project for JK has been started. /p /section +section name=Changes with JK 1.2.12 + br / + subsection name=Native +changelog + fixFix that worker not used, when stopped flag is true. (pero) + /fix + update + Add loadbalance default worker secret attribute to the documentation (pero) + /update +/changelog + /subsection +/section + section name=Changes with JK 1.2.11 br / subsection name=Native 1.16 +9 -0 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- workers.xml 29 Apr 2005 20:08:53 - 1.15 +++ workers.xml 5 May 2005 15:59:10 - 1.16 @@ -270,6 +270,15 @@ This feature has been added in bjk 1.2.9/b. /p /directive + +directive name=secret default= required=false +Set a default secret word for all defined workers. +See worker secret attribute description for more info. +p +This feature has been added in bjk 1.2.12/b. +/p +/directive + /directives /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2005/05/05 10:29:47 Modified:jk/xdocs/config workers.xml Log: Better describe cachesize. Revision ChangesPath 1.17 +8 -6 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- workers.xml 5 May 2005 15:59:10 - 1.16 +++ workers.xml 5 May 2005 17:29:47 - 1.17 @@ -151,15 +151,17 @@ directive name=cachesize default=1 required=false Cachesize defines the number of connections made to the AJP backend that are maintained as a connection pool. -It does not limit the number of those connection. +It will limit the number of those connection that each web server child +process can made. p -Cachesize property is useful when you're using JK in multi threaded +Cachesize property is used only for multi threaded web servers such as Apache 2.0 (worker), IIS and Netscape. The cachesize property -should reflect the number of threads per child process. The JK 1.2.8 will discover -the number of threads per child process on Apache 2 web server with worker-mpm. -For other web servers to will have to set that value manually. +should reflect the number of threads per child process. JK will discover +the number of threads per child process on Apache 2 web server with worker-mpm and set +its default value to match the ThreadsPerChild Apache directive. For IIS the default +value is 10. For other web servers this value has to be set manually. /p -warnDo not use cachesize with values higher then 1 on bprefork mpm/b or bapache 1.3.x/b!/warn +warnDo not use cachesize with values higher then 1 on bApache 2.x prefork/b or bApache 1.3.x/b!/warn /directive directive name=cache_timeout default=0 required=false - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
pero2005/04/29 13:08:53 Modified:jk/xdocs changelog.xml jk/xdocs/config workers.xml Log: Document the worker secret attribute. I hope we can update the site. Revision ChangesPath 1.27 +5 -1 jakarta-tomcat-connectors/jk/xdocs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/changelog.xml,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- changelog.xml 27 Apr 2005 14:06:17 - 1.26 +++ changelog.xml 29 Apr 2005 20:08:53 - 1.27 @@ -31,8 +31,12 @@ fixAdded missing SEARCH and ACL http methods. (mturk) /fix update + Add worker secret attribute to the documentation (pero) + /update + update Add a stopped flag to worker configuration. Set flag True and - complete traffic to worker is stopped. + complete traffic to worker is stopped. + Also update the Ant JkStatusUpdateTask at Tomcat 5.5.10 release. Only usefull in a replicated session cluster.(pero) /update updateAdded worker maintain function that will maintain all 1.15 +6 -0 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- workers.xml 26 Apr 2005 15:30:59 - 1.14 +++ workers.xml 29 Apr 2005 20:08:53 - 1.15 @@ -378,6 +378,12 @@ /p /directive +directive name=secret default= required=false +If set to AJP Connector secret keyword, only request with this keyword are successfull responding. +Use brequest.useSecret=true/b and brequest.secret=secret key word/b at your tomcat ajp +Connector configuration. +/directive + /directives /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
pero2005/04/26 08:30:59 Modified:jk/xdocs changelog.xml jk/xdocs/config workers.xml Log: Add stopped flag for better cluster support to worker. Many thanks to Mladen :- Revision ChangesPath 1.24 +5 -0 jakarta-tomcat-connectors/jk/xdocs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/changelog.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- changelog.xml 24 Apr 2005 10:15:02 - 1.23 +++ changelog.xml 26 Apr 2005 15:30:59 - 1.24 @@ -25,6 +25,11 @@ br / subsection name=Native changelog + update + Add a stopped flag to worker configuration. Set flag True and + complete traffic to worker is stopped. + Only usefull in a replicated session cluster.(pero) + /update updateAdded worker maintain function that will maintain all the workers instead just the current one. This enables to recycle the connections on all workers. (mturk) 1.14 +10 -0 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- workers.xml 25 Apr 2005 06:53:25 - 1.13 +++ workers.xml 26 Apr 2005 15:30:59 - 1.14 @@ -368,6 +368,16 @@ /p /directive +directive name=stopped default=False required=false +If set to bTrue/b or b1/b the worker will be stopped if member +of load balancer. The flag is needed for stop complete traffic of a sticky session +worker. It is only usefull, when you have a cluster that replicated the sessions. +This flag can be changed at runtime using status worker. +p +This feature has been added in bjk 1.2.11/b. +/p +/directive + /directives /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2005/04/24 03:43:27 Modified:jk/xdocs/config workers.xml Log: Add status worker directives section. Revision ChangesPath 1.11 +13 -1 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- workers.xml 23 Feb 2005 08:10:20 - 1.10 +++ workers.xml 24 Apr 2005 10:43:27 - 1.11 @@ -80,7 +80,7 @@ /p directives directive name=type default=ajp13 required=true -Type of the worker (can be one of ajp13, ajp14, jni or lb). The type of the worker +Type of the worker (can be one of ajp13, ajp14, jni, lb or status). The type of the worker defines the directives that can be applied to the worker. pAJP13 worker is the preferred worker type that JK uses for communication between web server and Tomcat. This type of worker uses sockets as communication @@ -270,6 +270,18 @@ /subsection +subsection name=Status Worker directives +br / +p +The status worker does not communicate with Tomcat. +Instead it is responsible for the load balancer management. +/p +directives +directive name=css default= required=false +Specifies the url for cascading stylesheet to use. +/directives +/subsection + subsection name=Advanced worker directives br / directives - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2005/04/24 03:47:28 Modified:jk/xdocs/config workers.xml Log: Add mising closing tag. Revision ChangesPath 1.12 +1 -0 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- workers.xml 24 Apr 2005 10:43:27 - 1.11 +++ workers.xml 24 Apr 2005 10:47:28 - 1.12 @@ -279,6 +279,7 @@ directives directive name=css default= required=false Specifies the url for cascading stylesheet to use. +/directive /directives /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
This email is in response to your job application. In order to be considered for this position, you must apply by visiting www.flexjobs.com/internal.asp. There you will find detailed instructions on how you can upload your resume to our jobs database for immediate consideration. Digiflex HR - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/12/13 01:26:12 Modified:jk/xdocs/config workers.xml Log: Explain load balance worker types Revision ChangesPath 1.6 +14 -5 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- workers.xml 25 Nov 2004 09:22:59 - 1.5 +++ workers.xml 13 Dec 2004 09:26:12 - 1.6 @@ -178,14 +178,19 @@ /subsection subsection name=Load balancing directives +br/ +pLoad balancer is a virtual worker that does not really communicate with Tomcat workers. +Instead it is responsible for the management of several real workers. +The worker is supposed to be a load balancer if it's worker type is blb/b. +See worker's btype/b directive. The workers that +are member of load balancer must not appear in the bworker.list/b directive. +/p pLoadbalancer directives defines the parameters needed to create a workers that are connectiong to a remote cluster of backend Tomcat servers. Each cluster node has to have a worker defined. /p p -The load-balancing worker does not really communicate with Tomcat workers. -Instead it is responsible for the management of several real workers. -This management includes: +Load balancer management includes: /p ul @@ -213,9 +218,13 @@ /p directives -directive name=balanced_workers required=true +directive name=balance_workers required=true A comma separated list of workers that the load balancer -need to manage. +need to manage. +p +This directive replaces old bbalanced_workers/b directive and +can be used only with mod_jk versions 1.2.7 and up. +/p warnThese workers should bnot/b appear in the worker.list property!/warn /directive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/12/14 00:48:07 Modified:jk/xdocs/config workers.xml Log: Explain some default values. Revision ChangesPath 1.7 +14 -13jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- workers.xml 13 Dec 2004 09:26:12 - 1.6 +++ workers.xml 14 Dec 2004 08:48:07 - 1.7 @@ -107,13 +107,14 @@ Port number of the remote Tomcat instance listening for defined protocol requests. /directive -directive name=socket_timeout default=infinite required=false +directive name=socket_timeout default=0 required=false Socket timeout in seconds used for communication channel between JK and remote host. If remote host does not respond inside that timeout the JK will generate an error, -and retry again. +and retry again. If set to value zero (default) the JK will wait for infinite +on all socket operations. /directive -directive name=socket_keepalive required=false +directive name=socket_keepalive default=False required=false This directive should be used when you have a firewall between your webserver and the Tomcat engine, who tend to drop inactive connections. This flag will told Operating System to send codeKEEP_ALIVE/code message on inactive connections (interval depend on global OS settings, @@ -125,13 +126,14 @@ /p /directive -directive name=recycle_timeout required=false +directive name=recycle_timeout default=0 required=false The number of seconds that told webserver to cut an ajp13 connection after some time of inactivity. When choosing an endpoint for a request and the assigned socket is open, it will be closed if it was not used for the configured time. It's a good way to ensure that there won't too old threads living on Tomcat side, with the extra cost you need to reopen the socket next time a request be forwarded. -This property is very similar to bcache_timeout/b but works also in non-cache mode. +This property is very similar to bcache_timeout/b but works also in non-cache mode. +If set to value zero (default) no recycle will took place. /directive directive name=retries default=3 required=false @@ -140,13 +142,13 @@ each retry after default an extra wait of 100ms will be inserted. /directive -directive name=cachesize default=0 required=false +directive name=cachesize default=1 required=false Cachesize property is usefull when you're using JK in multithreaded web servers such as Apache 2.0 (worker), IIS and Netscape. They will benefit the most by setting this value to a higher level (such as the estimated average concurrent users for Tomcat). If cachesize is not set, the connection cache support is disabled. Cachesize determines the minimum number of open connections to backend Tomcat. -warnDo not use cachesize with bprefork mpm/b or bapache 1.3.x/b!/warn +warnDo not use cachesize with values higer then 1 on bprefork mpm/b or bapache 1.3.x/b!/warn /directive directive name=cache_timeout default=0 required=false @@ -162,7 +164,7 @@ until killed. And since the webserver will keep its childs/threads running to handle high-load, even it the child/thread handle only static contents, you could finish having many unused ajp13 threads on the Tomcat side. -/p +/p. /directive directive name=lb_factor default=1 required=false @@ -173,7 +175,6 @@ that makes the load balancer. For example if one worker has lb_factor 5 times higher then other worker, then it will receive five times more requests. /directive - /directives /subsection @@ -218,7 +219,7 @@ /p directives -directive name=balance_workers required=true +directive name=balance_workers default= required=true A comma separated list of workers that the load balancer need to manage. p @@ -242,7 +243,7 @@ subsection name=Advanced worker directives directives -directive name=connect_timeout required=false +directive name=connect_timeout default=0 required=false Connect timeout property told webserver to send a PING request on ajp13 connection after connection is established. The parameter is the delay in milliseconds to wait for the PONG reply. p @@ -252,7 +253,7 @@ /p /directive -directive name=prepost_timeout required=false +directive name=prepost_timeout default=0 required=false Prepost timeout property told webserver to send a PING request on ajp13 connection before forwarding to it a request. The parameter is the delay in milliseconds to wait for the PONG reply. p @@ -262,7 +263,7 @@ /p /directive -directive name=reply_timeout required=false
Re: Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
This email is in response to your job application. In order to be considered for this position, you must apply by visiting www.flexjobs.com/internal.asp. There you will find detailed instructions on how you can upload your resume to our jobs database for immediate consideration. Digiflex HR - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/11/25 01:22:59 Modified:jk/xdocs/config workers.xml Log: Add more workers directives to doc. Revision ChangesPath 1.5 +200 -5jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- workers.xml 22 Nov 2004 16:51:44 - 1.4 +++ workers.xml 25 Nov 2004 09:22:59 - 1.5 @@ -61,6 +61,19 @@ /warn /p +subsection name=Defining workers +pDefining workers to the Tomcat web server plugin can be done using a properties file +(a sample file named workers.properties is available in the conf/ directory). +/p +directives +directive name=worker.list required=true +A comma separated list of workers names that the JK will use. When starting up, +the web server plugin will instantiate the workers whose name appears in the +worker.list property, these are also the workers to whom you can map requests. +/directive +/directives +/subsection + subsection name=Mandatory directives pMandatory directives are the one that each worker bmust/b contain. Without them the worker will be unavailable or will misbehave. @@ -69,15 +82,18 @@ directive name=type default=ajp13 required=true Type of the worker (can be one of ajp13, ajp14, jni or lb). The type of the worker defines the directives that can be applied to the worker. +pAJP13 worker is the preferred worker type that JK uses for communication +between web server and Tomcat. This type of worker uses sockets as communication +channel. For detailed description of the AJP13 protocol stack browse to +a href=../common/ajpv13a.htmlAJPv13 protocol specification/a +/p /directive /directives /subsection -subsection name=AJP13 worker directives -pAJP13 worker directives are the preferred worker type that JK uses for communication -between web server and Tomcat. This type of worker uses sockets as communication -channel. For detailed description of the AJP13 protocol stack browse to -a href=../common/ajpv13a.htmlAJPv13 protocol specification/a +subsection name=Connection directives +pConnection directives defines the parameters needed to connect and maintain +the connections pool of persisten connections between JK and remote Tomcat. /p directives @@ -130,6 +146,7 @@ setting this value to a higher level (such as the estimated average concurrent users for Tomcat). If cachesize is not set, the connection cache support is disabled. Cachesize determines the minimum number of open connections to backend Tomcat. +warnDo not use cachesize with bprefork mpm/b or bapache 1.3.x/b!/warn /directive directive name=cache_timeout default=0 required=false @@ -148,11 +165,189 @@ /p /directive +directive name=lb_factor default=1 required=false +Integer number used when the worker will be used inside load balancer worker, +this is the load-balancing factor for the worker. +The load-balancing factor is ihow much we expect this worker to work/i, or +ithe worker's work quota/i. Load balancing factor is compared with other workers +that makes the load balancer. For example if one worker has lb_factor 5 times higher then +other worker, then it will receive five times more requests. +/directive + +/directives +/subsection + +subsection name=Load balancing directives +pLoadbalancer directives defines the parameters needed to create a workers that are +connectiong to a remote cluster of backend Tomcat servers. Each cluster node has to +have a worker defined. +/p +p +The load-balancing worker does not really communicate with Tomcat workers. +Instead it is responsible for the management of several real workers. +This management includes: +/p + +ul +li +Instantiating the workers in the web server. +/li +li +Using the worker's load-balancing factor, perform weighed-round-robin load balancing where +high lbfactor means stronger machine (that is going to handle more requests) +/li +li +Keeping requests belonging to the same session executing on the same Tomcat worker. +/li +li +Identifying failed Tomcat workers, suspending requests to them and instead fall-backing on +other workers managed by the lb worker. +/li +/ul + +p +The overall result is that workers managed by the same lb worker are load-balanced +(based on their lbfactor and current user session) and also fall-backed so a single +Tomcat process death will not kill the entire site. +The following table specifies properties that the lb worker can accept: +/p + +directives +directive name=balanced_workers required=true +A comma separated list of workers that the load balancer +need to
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/11/22 08:51:44 Modified:jk/xdocs/config workers.xml Log: More workers properties documented. Revision ChangesPath 1.4 +28 -0 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- workers.xml 19 Nov 2004 10:39:36 - 1.3 +++ workers.xml 22 Nov 2004 16:51:44 - 1.4 @@ -103,6 +103,10 @@ to send codeKEEP_ALIVE/code message on inactive connections (interval depend on global OS settings, generally 120ms), and thus prevent the firewall to cut the connection. To enable keepalive set this property value to the number greater then b0/b. +p +The problem with Firewall cutting inactive connections is that sometimes, neither webserver or tomcat +have informations about the cut and couldn't handle it. +/p /directive directive name=recycle_timeout required=false @@ -118,6 +122,30 @@ The number of retries that the worker will try in case of error returned from remote Tomcat. If the number of retries set is greater then three (the default value), on each retry after default an extra wait of 100ms will be inserted. +/directive + +directive name=cachesize default=0 required=false +Cachesize property is usefull when you're using JK in multithreaded +web servers such as Apache 2.0 (worker), IIS and Netscape. They will benefit the most by +setting this value to a higher level (such as the estimated average concurrent users for Tomcat). +If cachesize is not set, the connection cache support is disabled. +Cachesize determines the minimum number of open connections to backend Tomcat. +/directive + +directive name=cache_timeout default=0 required=false +Cache timeout property should be used with bcachesize/b to specify how to time JK should keep +an open socket in cache before closing it. This property should be used to reduce the number of threads +on the Tomcat WebServer. +p +Each child could open an ajp13 connection if it have to forward a request to Tomcat, creating +a new ajp13 thread on Tomcat side. +/p +p +The problem is that after an ajp13 connection is created, the child won't drop it +until killed. And since the webserver will keep its childs/threads running +to handle high-load, even it the child/thread handle only static contents, you could +finish having many unused ajp13 threads on the Tomcat side. +/p /directive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/11/19 01:31:20 Modified:jk/xdocs/config workers.xml Log: Start documenting all worker.properties directives Revision ChangesPath 1.2 +73 -4 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml Index: workers.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- workers.xml 18 Nov 2004 18:28:54 - 1.1 +++ workers.xml 19 Nov 2004 09:31:20 - 1.2 @@ -13,10 +13,79 @@ body -section name=Work in progress -To be finished! - -/section +section name=Introduction +p +A bTomcat worker/b is a Tomcat instance that is waiting to execute servlets or any other content +on behalf of some web server. For example, we can have a web server such as +Apache forwarding servlet requests to a Tomcat process (the worker) running behind it. +/p +p +The scenario described above is a very simple one; +in fact one can configure multiple Tomcat workers to serve servlets on +behalf of a certain web server. +The reasons for such configuration can be: +/p +ul +li +We want different contexts to be served by different Tomcat workers to provide a +development environment where all the developers share the same web server but +own a Tomcat worker of their own. +/li +li +We want different virtual hosts served by different Tomcat processes to provide a +clear separation between sites belonging to different companies. +/li +li +We want to provide load balancing, meaning run multiple Tomcat workers each on a +machine of its own and distribute the requests between them. +/li +/ul + +p +There are probably more reasons for having multiple workers but I guess that this list is enough... +Tomcat workers are defined in a properties file dubbed bworkers.properties/b and this tutorial +explains how to work with it. +/p +/section + +section name=Directives +pEach workers.properties directive consists of three words separated by dot. The first word is always +bworker/b. The second word is the worker name that can be any name. The worker name reflects the +name of the bjvmRoute/b defined in Tomcat's server.xml configuration file. +/p +p +warn +The name of the worker can contain only the alphanumeric characters b[a-z][A-Z][0-9]/b and is case insensitive. +/warn +/p + +subsection name=Mandatory directives +pMandatory directives are the one that each worker bmust/b contain. Without them the worker will +be unavailable or will missbehave. +/p +directives +directive name=type required=true +Type of the worker (can be one of ajp13, jni or lb). The type of the worker +defines the directives that can be applied to the worker. +/directive +/directives +/subsection + +subsection name=AJP13 worker directives +pAJP13 worker directives are the preferred worker type that JK uses for communication +between web server and Tomcat. This type of worker uses sockets as communication +channel. +/p +directives +directive name=host required=true +Host name or IP address of the backend Tomcat instance. The remote Tomcat must +support the ajp13 protocol. +/directive +/directives +/subsection + + +/section /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml
mturk 2004/11/19 02:39:36
Modified:jk/xdocs/config workers.xml
Log:
More workers configuration documented
Revision ChangesPath
1.3 +46 -6 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml
Index: workers.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- workers.xml 19 Nov 2004 09:31:20 - 1.2
+++ workers.xml 19 Nov 2004 10:39:36 - 1.3
@@ -46,6 +46,8 @@
Tomcat workers are defined in a properties file dubbed
bworkers.properties/b and this tutorial
explains how to work with it.
/p
+pThe generic workers.properties directive is in the form:/p
+pstrongworker.lt;worker
namegt;.lt;directivegt;=lt;valuegt;/strong/p
/section
section name=Directives
@@ -61,11 +63,11 @@
subsection name=Mandatory directives
pMandatory directives are the one that each worker bmust/b contain.
Without them the worker will
-be unavailable or will missbehave.
+be unavailable or will misbehave.
/p
directives
-directive name=type required=true
-Type of the worker (can be one of ajp13, jni or lb). The type of the worker
+directive name=type default=ajp13 required=true
+Type of the worker (can be one of ajp13, ajp14, jni or lb). The type of the
worker
defines the directives that can be applied to the worker.
/directive
/directives
@@ -74,13 +76,51 @@
subsection name=AJP13 worker directives
pAJP13 worker directives are the preferred worker type that JK uses for
communication
between web server and Tomcat. This type of worker uses sockets as
communication
-channel.
+channel. For detailed description of the AJP13 protocol stack browse to
+a href=../common/ajpv13a.htmlAJPv13 protocol specification/a
/p
directives
-directive name=host required=true
+
+directive name=host default=localhost required=true
Host name or IP address of the backend Tomcat instance. The remote Tomcat
must
-support the ajp13 protocol.
+support the ajp13 protocol stack. The host name can have a bport/b number
+embedded separated by the colon (':') character.
+/directive
+
+directive name=port default=8009 required=false
+Port number of the remote Tomcat instance listening for defined protocol
requests.
+/directive
+
+directive name=socket_timeout default=infinite required=false
+Socket timeout in seconds used for communication channel between JK and
remote host.
+If remote host does not respond inside that timeout the JK will generate an
error,
+and retry again.
+/directive
+
+directive name=socket_keepalive required=false
+This directive should be used when you have a firewall between your webserver
+and the Tomcat engine, who tend to drop inactive connections. This flag will
told Operating System
+to send codeKEEP_ALIVE/code message on inactive connections (interval
depend on global OS settings,
+generally 120ms), and thus prevent the firewall to cut the connection.
+To enable keepalive set this property value to the number greater then
b0/b.
/directive
+
+directive name=recycle_timeout required=false
+The number of seconds that told webserver to cut an ajp13 connection after
some time of
+inactivity. When choosing an endpoint for a request and the assigned socket
is open, it will be
+closed if it was not used for the configured time.
+It's a good way to ensure that there won't too old threads living on Tomcat
side,
+with the extra cost you need to reopen the socket next time a request be
forwarded.
+This property is very similar to bcache_timeout/b but works also in
non-cache mode.
+/directive
+
+directive name=retries default=3 required=false
+The number of retries that the worker will try in case of error returned
from remote
+Tomcat. If the number of retries set is greater then three (the default
value), on
+each retry after default an extra wait of 100ms will be inserted.
+/directive
+
+
/directives
/subsection
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
