Package: libapache2-mod-jk
Version: 1:1.2.37-1
Severity: important
Tags: patch

Dear Maintainer,

A more detailed description of the problem including discussion 
can be found at:

In short:
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:

--- libapache-mod-jk-1.2.37.orig/native/common/jk_status.c
+++ libapache-mod-jk-1.2.37/native/common/jk_status.c
@@ -3647,7 +3647,7 @@ static void commit_all_members(jk_ws_ser
             if (sync_needed == JK_TRUE) {
-                wr->sequence = 0;
+                wr->sequence = -1;
                 if (!rc)
                     rc = 3;

Please consider backporting this patch to Wheezy, because the
worker activation state is completely unusable as it is now, and
this is probably an important feature for many users of this

Thanks & best regards,

David Gubler

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libapache2-mod-jk depends on:
ii  apache2.2-common  2.2.22-13
ii  libc6             2.13-38

libapache2-mod-jk recommends no packages.

Versions of packages libapache2-mod-jk suggests:
pn  libapache-mod-jk-doc  <none>
pn  tomcat6               <none>

-- Configuration Files:
/etc/libapache2-mod-jk/ changed [not included]

-- no debconf information

This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to