1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
Description: Worker activation state corrupted when using jkmanager
We use jkmanager to selectively disable (DIS state) workers to do
rolling releases. This worked fine in Squeeze (mod_jk 1.2.30),
but does not work properly anymore in Wheezy (mod_jk 1.2.37). The
effect is: When I set a worker to disabled, it flips back and forth
between disabled an active, and the load on the worker does not
decrease as it should. Same with stopped. Happens on multiple
Apache servers independently.
.
The following change from the upcoming 1.2.38 release fixes the
problem at least for our setup.
.
<URL:http://tomcat.10.x6.nabble.com/mod-jk-worker-activation-not-working-anymore-in-1-2-37-td4999956.html>
Author: David Gubler <dg@doodle.com>
Last-Update: 2013-08-12
Bug: http://bugs.debian.org/cgi-bin/711934
--- a/native/common/jk_status.c
+++ b/native/common/jk_status.c
@@ -3647,7 +3647,7 @@
}
}
if (sync_needed == JK_TRUE) {
- wr->sequence = 0;
+ wr->sequence = -1;
if (!rc)
rc = 3;
}
|
