Bug#609886: Fwd: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Miguel Landaeta]

-- Forwarded message --
From: Vamegh Hedayati 
Date: Thu, Jan 20, 2011 at 6:33 PM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Miguel Landaeta 


Hi Miguel,

This I think is a definite bug, sorry I replied to the thread, but it
hasnt shown up, sorry if you already have seen this.

I had this exact same issue over the last 2 days, I upgraded my server
to Debian unstable and it would constantly give me the same error as
eyck.

I did also notice that the following line:



Had been commented out and re-enabled it, checked using lsof saw the
port running verified it, but would still get the same error in mod_jk
log file.

I then installed tomcat7 and still had the same issue and was
searching for the problem and came across this bug report.

To test if this was in fact the issue, I downloaded the binary
mod_jk.so from apache website directly, from:

wget 
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/linux/jk-1.2.31/x86_64/mod_jk-1.2.31-httpd-2.2.x.so

Using this all of my problems are now solved and it works.

The mod_jk I was using is as follows:

apt-cache show libapache2-mod-jk
Package: libapache2-mod-jk
Priority: optional
Section: net
Installed-Size: 380
Maintainer: Debian Java Maintainers 
Architecture: amd64
Source: libapache-mod-jk
Version: 1:1.2.26-2+lenny1
Replaces: libapache2-mod-jk2
Depends: libc6 (>= 2.7-1), apache2.2-common, apache2
Suggests: tomcat5.5, libapache-mod-jk-doc
Conflicts: libapache2-mod-jk2
Filename: pool/main/liba/libapache-mod-jk/libapache2-mod-
jk_1.2.26-2+lenny1_amd64.deb
Size: 127806
MD5sum: 84fe833769ac2a4cda17fb6f48b3ca6d
SHA1: a71b97b35d5b1fb5c1fd075bba64b01481baf16e
SHA256:
1729cd1f48e633830bacea9a2fdc8e57bd7b635aed133f5dbcb683b8cf634b8e
Description: Apache 2 connector for the Tomcat Java servlet engine
 Apache Tomcat is the reference implementation for the Java Servlet
and
 JavaServer Pages (JSP) specification from the Apache Jakarta project.
 .
 This package contains an Apache 2 module (mod_jk) to forward requests
 from Apache to Tomcat using the AJP 1.3 or 1.4 protocol. It can
either
 talk to Tomcat on the local machine or to a remote engine using TCP.
Homepage: http://tomcat.apache.org/
Tag: role::shared-lib, suite::apache

Package: libapache2-mod-jk
Priority: optional
Section: httpd
Installed-Size: 508
Maintainer: Debian Java Maintainers 
Architecture: amd64
Source: libapache-mod-jk
Version: 1:1.2.30-1
Replaces: libapache2-mod-jk2
Depends: libc6 (>= 2.3), apache2.2-common, apache2
Suggests: tomcat6, libapache-mod-jk-doc
Conflicts: libapache2-mod-jk2
Filename: pool/main/liba/libapache-mod-jk/libapache2-mod-
jk_1.2.30-1_amd64.deb
Size: 148966
MD5sum: 49b4fa9b59f3a6df6441c19cb3345e13
SHA1: b8d396d5be2189c0e45ce0a394625f332fc8c69d
SHA256:
38479b41a41e7c436b90b240ccf15819fee8215d2bc37f6b8d5e0e684a580b8c
Description: Apache 2 connector for the Tomcat Java servlet engine
 Apache Tomcat is the reference implementation for the Java Servlet
and
 JavaServer Pages (JSP) specification from the Apache Jakarta project.
 .
 This package contains an Apache 2 module (mod_jk) to forward requests
 from Apache to Tomcat using the AJP 1.3 or 1.4 protocol. It can
either
 talk to Tomcat on the local machine or to a remote engine using TCP.
Homepage: http://tomcat.apache.org/
Tag: role::shared-lib, suite::apache

I hope this helps, but I definitely think there is an issue with the
current unstable version of mod_jk it has communication issues, I
tried several tests over the last couple of days, so I am pretty
confident there is a bug with it.

If you need anything else from me please let me know, I can forward
you all of my logs or anything else you need.

All the best,


v


On Jan 17, 11:30 pm, Miguel Landaeta  wrote:
> On Mon, Jan 17, 2011 at 6:00 PM, Damien Raude-Morvan
>
>  wrote:
> > I don't think it's properly documented in tomcat6 and/or libapache2-mod-jk
> > Debian packages. Maybe you could add a note inside README.Debian (although
> > it's not really specific to Debian).
>
> Sure. Good idea.
> I'll add that to my to-do list.
> This issue will remain open until that is clarified in the documentation.
> Cheers,
>
> --
> Miguel Landaeta, miguel at miguel.cc
> secure email with PGP 0x7D8967E9 available athttp://keyserver.pgp.com/
> "Faith means not wanting to know what is true." -- Nietzsche
>
> --
> To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org




-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche



__
This is the maintainer address of Debian's Java team
. Please 
use
debian-j...@lists.debian.org for discussions and questions.

Bug#609886: Fwd: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Miguel Landaeta]

-- Forwarded message --
From: Vamegh Hedayati 
Date: Fri, Jan 21, 2011 at 8:03 AM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Miguel Landaeta 


Hi Miguel,

I guess the best way I can replicate this is to switch back to the
mod_jk from debian and show you what happens.

My setup is completely default. I am using openjdk and apache2.2 from
debian unstable, the server is
just my own play server and as far as web is concerned it is basically
a completely fresh install.

my website is www.vamegh.co.uk

I have the following in /etc/apache2/conf.d/jk.conf


 # Where to find workers.properties
 # Update this path to match your conf directory location (put
workers.properties next to httpd.conf)
 JkWorkersFile /etc/apache2/workers.properties
 # Where to put jk shared memory
 # Update this path to match your local state directory or logs directory
 # JkShmFile     /var/log/apache2/mod_jk.shm
 # Where to put jk logs
 # Update this path to match your logs directory location (put
mod_jk.log next to access_log)
 JkLogFile     /var/log/apache2/mod_jk.log
 # Set the jk log level [debug/error/info]
 JkLogLevel    debug
 # Select the timestamp log format
 # JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
 # Send everything for context /examples to worker named worker1 (ajp13)
 # JkMount  /examples/* worker1



I downloaded the binary mod_jk from apache as I already mentioned and
put it into:

ls -al /usr/lib/apache2/modules/|grep mod_jk
-rw-r--r-- 1 root root 394007 Nov  1 05:42 mod_jk-1.2.31-httpd-2.2.x.so
lrwxrwxrwx 1 root root     28 Jan 20 19:24 mod_jk2.so ->
mod_jk-1.2.31-httpd-2.2.x.so
-rw-r--r-- 1 root root 421760 Jul 24 01:08 mod_jk.so

and in

cat /etc/apache2/mods-enabled/jk.load
LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so

All I do is switch mod_jk.so to mod_jk2.so to run the apache
pre-compiled binary vs the debian provided binary.. So if everything
else is equal we know that the only changing thing is this jk
connector.

Now, just to test I have switched it back to mod_jk.so and I get the
following when trying to visit www.vamegh.co.uk/test.jsp

tail -f /var/log/apache2/mod_jk.log
[Fri Jan 21 13:14:43.761 2011] [19849:140364869056320] [debug]
uri_worker_map_dump::jk_uri_worker_map.c (186): NEXT (1) map #0:
uri=/*.jsp worker=default context=/*.jsp source=JkMount type=Wildchar
len=6
[Fri Jan 21 13:14:43.761 2011] [19849:140364869056320] [debug]
uri_worker_map_switch::jk_uri_worker_map.c (482): Switching uri worker
map from index 0 to index 1
[Fri Jan 21 13:14:43.762 2011] [19851:140364869056320] [debug]
do_shm_open::jk_shm.c (550): Attached shared memory
/var/log/apache2/jk-runtime-status.19849 [2] size=448 free=0
addr=0x7fa93e295000
[Fri Jan 21 13:14:43.763 2011] [19851:140364869056320] [debug]
do_shm_open::jk_shm.c (564): Resetting the shared memory for child 2
[Fri Jan 21 13:14:43.763 2011] [19851:140364869056320] [debug]
do_shm_open_lock::jk_shm.c (353): Duplicated shared memory lock
/var/log/apache2/jk-runtime-status.19849.lock
[Fri Jan 21 13:14:43.763 2011] [19851:140364869056320] [debug]
jk_child_init::mod_jk.c (3073): Initialized mod_jk/1.2.30
[Fri Jan 21 13:14:43.765 2011] [19856:140364869056320] [debug]
do_shm_open::jk_shm.c (550): Attached shared memory
/var/log/apache2/jk-runtime-status.19849 [3] size=448 free=320
addr=0x7fa93e295000
[Fri Jan 21 13:14:43.765 2011] [19856:140364869056320] [debug]
do_shm_open::jk_shm.c (564): Resetting the shared memory for child 3
[Fri Jan 21 13:14:43.765 2011] [19856:140364869056320] [debug]
do_shm_open_lock::jk_shm.c (353): Duplicated shared memory lock
/var/log/apache2/jk-runtime-status.19849.lock
[Fri Jan 21 13:14:43.765 2011] [19856:140364869056320] [debug]
jk_child_init::mod_jk.c (3073): Initialized mod_jk/1.2.30










[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map
URI '/test.jsp' from 1 maps
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
find_match::jk_uri_worker_map.c (850): Attempting to map context URI
'/*.jsp=default' source 'JkMount'
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
find_match::jk_uri_worker_map.c (863): Found a wildchar match
'/*.jsp=default'
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
jk_handler::mod_jk.c (2462): Into handler jakarta-servlet
worker=default r->proxyreq=0
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
wc_get_worker_for_name::jk_worker.c (116): found a worker default
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
wc_maintain::jk_worker.c (339): Maintaining worker default
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
wc_get_name_for_type::jk_worker.c (293): Found worker type 'ajp13'
[Fri Jan 21 13:15:17.954 2011] [19851:140364785633040] [debug]
init_ws_service::mod_jk.c (978): Service protocol=HTTP/1.1 method=GET
ssl=false host=(null) addr=92.7.

Bug#609886: Fwd: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Miguel Landaeta]

-- Forwarded message --
From: Miguel Landaeta 
Date: Fri, Jan 21, 2011 at 10:54 AM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Vamegh Hedayati 


Thanks Vamegh,

I'll work on this during the weekend and I'll let you know
what I find.

Regards,


-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche



__
This is the maintainer address of Debian's Java team
. Please 
use
debian-j...@lists.debian.org for discussions and questions.

Bug#609886: Fwd: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Miguel Landaeta]

tags 609886 unreproducible
thanks

On Fri, Jan 21, 2011 at 05:45:13PM -0430, Miguel Landaeta wrote:
> I'll work on this during the weekend and I'll let you know
> what I find.

I tried again to reproduce this in a KVM virtual machine
but I couldn't.

The only things I can do for this bug report are to document
how to enable the AJP connector in tomcat6 as suggested
Damien and prepare a updated package.

This is kind of off-topic for this bug but did you tried
with mod_proxy_ajp included with Apache 2.2? I maintain a
production website using tomcat6 and that module without
issues. That could be another option.

Regards,

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche



__
This is the maintainer address of Debian's Java team
. Please 
use
debian-j...@lists.debian.org for discussions and questions.