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

[Miguel Landaeta]

severity 609886 normal
thanks

On Mon, Jan 17, 2011 at 12:26:15AM +0100, eyck wrote:
>  This was detected on soon-to-become-production server, and then reproduced
> by using clean template, performing upgrade of libapache2_mod_jk, and then
> downgrade fixes the problem. Both machines came from the same template, I
> need some time to verify whether the problem is related to the template or
> not.
> 
> > In a clean lenny chroot I installed apache2, tomcat5.5,
> > tomcat5.5-webapps, and libapache2-mod-jk. After that
>  The problem was detected with tomcat6, but I tried connecting to tomcat5.5
> running on another machine, and this confusing 'failed opening socket'

Hi Dariusz,

I'm convinced this is not a bug. I explain:

I was able to reproduce this issue installing apache2,
tomcat6 and libapache2-mod-jk but I noticed that tomcat6
by default doesn't listen on port 8009 so libapache2-mod-jk
fails to connect with tomcat6.

After I enabled that port on tomcat6 configuration
(server.xml) libapache2-mod-jk was able to connect with
tomcat6 and the upgrade from 1.2.26 to 1.2.30 happened
without any issue.

I'm downgrading the severity of this bug and I'll close
it after you confirm this issue is solved.

Cheers,

-- 
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