tags 609886 + moreinfo thanks On Thu, Jan 13, 2011 at 03:49:12PM +0100, eyck wrote: > Package: libapache2-mod-jk > Version: 1.2.30 > Severity: grave > Justification: renders package unusable > > >>From mod_jk.log: > [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] > jk_open_socket::jk_connect.c (444): socket() failed (errno=22) > [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] > ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to > (172.17.231.57:8009) (errno=22) > [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] > ajp_send_request::jk_ajp_common.c (1585): (ajp13) connecting to backend > failed. Tomcat is probably not started or is listening on the wrong port > (errno=22) > [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] > ajp_service::jk_ajp_common.c (2540): (ajp13) sending request to tomcat failed > (recoverable), because of error during request sending (attempt=1) > [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] > ajp_service::jk_ajp_common.c (2559): (ajp13) connecting to tomcat failed. > although logs suggest that port 8009 is unreachable, > one can connect to it using telnet, or by replacing libapache2_mod_jk with > version 1.2.26
I tried to reproduce this error and I couldn't. In a clean lenny chroot I installed apache2, tomcat5.5, tomcat5.5-webapps, and libapache2-mod-jk. After that I setup a trivial test website. I upgraded libapache2-mod-jk to 1.2.30-1 and the website keeps working. There were not errors at mod_jk.log. In another clean lenny chroot configured in the same way and after doing a dist-upgrade to squeeze (and also upgrading libapache2-mod-jk to 1.2.30-1), the website keeps working. There were not errors at mod_jk.log. Note: my workstation is an amd64. 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
