> > >>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. 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' > Note: my workstation is an amd64. Same platform - opteron running 64bit kernel. best regards, Dariusz Pietrzak -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Total Existance Failure -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
