Not sure what happened here. The app was working just fine until today. I am getting a 503 Service temporarily unavailable error when trying to connect to a tomcat site using Apache as the front end and mod_jk connectors. I have verified that tomcat is running on the correct ports using:netstat -atp | grep java and it is listening on the correct ports. I see no errors in the message logs ( we are on CentOS by the way ) but I do see:

 [Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Wed Aug 03 18:49:24 2011] [15605:1199618400] [error] ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
[Wed Aug 03 18:49:24 2011] exodus www.exodusdecoded.com 0.198512
[Wed Aug 03 18:49:24 2011] [15605:1199618400] [info] jk_handler::mod_jk.c (2618): Service error=-3 for worker=exodus
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (174.122.30.18:8010) (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_send_request::jk_ajp_common.c (1585): (exodus) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_open_socket::jk_connect.c (622): connect to 174.122.30.18:8010 failed (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (174.122.30.18:8010) (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_send_request::jk_ajp_common.c (1585): (exodus) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] ajp_service::jk_ajp_common.c (2540): (exodus) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [error] ajp_service::jk_ajp_common.c (2559): (exodus) connecting to tomcat failed.
[Wed Aug 03 18:50:46 2011] exodus www.exodusdecoded.com 0.197989
[Wed Aug 03 18:50:46 2011] [15851:1189128544] [info] jk_handler::mod_jk.c (2618): Service error=-3 for worker=exodus

in the mod_jk.log file. Apache is running. I am stumped but really need to get this back running if anyone outhere is more experienced at tomcat and apache connectors than I am, which wouldn't take much ;-)

Cheers,

Dave

link|improve this question
Is there a firewall in place now? You could put on verbose debugging for the jk connector and look in the log to see what is going on. – James Black Aug 3 '11 at 23:05
see similar issue here on Centos - 2nd last post forums.atlassian.com/… – shinynewbike Aug 4 '11 at 6:24
... did you restart Tomcat already? – Janne Pikkarainen Aug 5 '11 at 10:22
It looks like your tomcat ajp connector stopped accepting requests (or is configured wrong). If a restart of tomcat doesn't restore service, can you post the relevant sections for mod_jk from your httpd.conf and your workers.properties files? Also, how big is your workers.properties file? – mahnsc Aug 5 '11 at 20:38
feedback

migrated from stackoverflow.com Aug 5 '11 at 10:13

This question came from our site for professional and enthusiast programmers.

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown