https://issues.apache.org/bugzilla/show_bug.cgi?id=48191
--- Comment #2 from Rainer Jung <rainer.j...@kippdata.de> 2009-11-13 03:27:09 UTC --- This looks like mod_jk received the full response from the backend and could successfully send it to the client. Unfortunately the problem you originally reported on the users list was very different, namely you found an error in the jk log file: [Tue Nov 03 11:03:07 2009] [12138:2537062720] [info] ajp_connection_tcp_get_message::jk_ajp_common.c (1150): (worker_portfolio_son1) can't receive the response header message from tomcat, network problems or tomcat (172.23.17.37:8009) is down (errno=11) [Tue Nov 03 11:03:07 2009] [12138:2537062720] [error] ajp_get_reply::jk_ajp_common.c (1962): (worker_portfolio_son1) Tomcat is down or refused connection. No response has been sent to the client (yet) [Tue Nov 03 11:03:07 2009] [12138:2537062720] [info] ajp_service::jk_ajp_common.c (2447): (worker_portfolio_son1) sending request to tomcat failed (recoverable), (attempt=2) [Tue Nov 03 11:03:07 2009] [12138:2537062720] [error] ajp_service::jk_ajp_common.c (2466): (worker_portfolio_son1) connecting to tomcat failed. [Tue Nov 03 11:03:07 2009] worker_portfolio_son1 citibank-extranet-ru-test.civ-versicherung.de 244.108419 [Tue Nov 03 11:03:07 2009] [12138:2537062720] [info] jk_handler::mod_jk.c (2615): Service error=0 for worker=worker_portfolio_son1 Here errno=11 meens EAGAIN. You also originally reported that this problem doesn't occur with version 1.2.26: Working: mod_jk 1.2.26: Server version: Apache/2.0.46 Red Hat Enterprise Linux ES release 3 (Taroon Update 5) 32 bit Broken: mod_jk 1.2.28: Server version: Apache/2.0.52 Red Hat Enterprise Linux ES release 4 (Nahant Update 8) 64 bit Indeed the return code EAGAIN when reading from the backend socket was handled in a special way until 1.2.26 and is no longer in 1.2.28. We removed tolerating EAGAIN while reading from the backend: http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_connect.c?r1=705959&r2=705977&pathrev=802161&diff_format=h EAGAIN should only be returned by read() when the socket is set to non-blocking mode. I can't see why this should be the case for your configuration. To not confuse any longer: Can you reproduce the problem under the following circumstances: - no reply_timeout - no coekcet_timeout - with at least one line of "[error]" in the JK log If so, what's the request, what's in the JK log, what's the config in that case? I actually don't care whether it's a PDF request or not as long as we know what's being tested and the above conditions are met. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
