Hi Enrico, I think we will have fixed your original problem, and also the sendfull/another log lines in 1.2.20. They don't mean anything bad, so please ignore them for the moment. Watch the list, we will have a 1.2.20 release ready for testing next week.
Concerning the client write error, this usually neans, that the response of a request could not be sent successfully to the client. Typically the client is a browser and most often the source of the problem is a request that runs for a longer time, than exected by the user. So the user presses "Again" or clicks on another link. The browser then closes the current connection and starts a new one. Trying to send back addinitional response packets for the first request then detects the closed connection and throws an info message. If this explanation fits into what you are experiencing, then you can ignore these messages two. They won't go away in 1.2.20, because it is important to know, if this happens only rarely, or very often. In the apache access log you can log the response times with %D so you can get an idea, if most occurences relate to long running requests. Regards, Rainer Enrico Donelli schrieb: > Sorry, here the answers > >> Do you also observe a real problem, or only the info log messages. Do >> the requests actually fail? > > Only in log files. No visible problems. But every couple of weeks > (about, not always) the connector completely hangs apache. > > >> Now to your problem: Please add >> worker.ajp13.socket_timeout=0 > > I added it. > Now the errors are: > > > [Sat Nov 18 22:43:13 2006] [28124:7072] [error] > ajp_connection_tcp_send_message::jk_ajp_common.c (914): sendfull > returned -32 with errno=32 > [Sat Nov 18 22:43:13 2006] [28124:7072] [info] > ajp_send_request::jk_ajp_common.c (1194): (ajp13) error sending > request. Will try another pooled connection > > or > > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] > ajp_process_callback::jk_ajp_common.c (1410): Writing to client > aborted or client network problems > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] > ajp_service::jk_ajp_common.c (1795): (ajp13) request failed, because > of client write error without recovery in send loop attempt=0 > [Sat Nov 18 22:08:36 2006] ajp13 www.scandinaviadesign.it 24.124384 > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] jk_handler::mod_jk.c > (2056): Aborting connection for worker=ajp13 > > > I attach the mod_ik logs, with trace enabled, the second with trace > enabled. > > > Thanks again!!! > > Enrico > > > On 18/11/06, Rainer Jung <[EMAIL PROTECTED]> wrote: >> Hi Enrico, >> >> would you be so kind and answer some of the questions in my previous >> mails, before we proceed to further questions from your side :) >> >> Regards, >> >> Rainer >> >> Enrico Donelli schrieb: >> > Thanks a lot for your help Rainer, I really appreciate. >> > >> > From time to time (every couple of weeks) the connector completely >> > hangs apache. Tomcat alone is still alive, but apache no longer >> > replies to requests, and I need to restart both >> > >> > Now it's working properly, but there are still many error in log files: >> > >> > [Sat Nov 18 22:43:13 2006] [28124:7072] [error] >> > ajp_connection_tcp_send_message::jk_ajp_common.c (914): sendfull >> > returned -32 with errno=32 >> > [Sat Nov 18 22:43:13 2006] [28124:7072] [info] >> > ajp_send_request::jk_ajp_common.c (1194): (ajp13) error sending >> > request. Will try another pooled connection >> > >> > or >> > >> > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] >> > ajp_process_callback::jk_ajp_common.c (1410): Writing to client >> > aborted or client network problems >> > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] >> > ajp_service::jk_ajp_common.c (1795): (ajp13) request failed, because >> > of client write error without recovery in send loop attempt=0 >> > [Sat Nov 18 22:08:36 2006] ajp13 www.scandinaviadesign.it 24.124384 >> > [Sat Nov 18 22:08:36 2006] [27825:7072] [info] jk_handler::mod_jk.c >> > (2056): Aborting connection for worker=ajp13 >> > >> > Thanks again!!! >> > >> > Enrico >> > >> > On 18/11/06, Rainer Jung <[EMAIL PROTECTED]> wrote: >> >> Adding to my own comments: I think I found a problem. So one more >> >> question: >> >> >> >> Do you also observe a real problem, or only the info log messages. Do >> >> the requests actually fail? >> >> >> >> >> >> Regards, >> >> >> >> Rainer >> >> >> >> Enrico Donelli schrieb: >> >> > Thanks Rainer for your reply! >> >> > >> >> > Here's my mod_jk.conf >> >> > >> >> > I solved my previous error adding the directive >> >> > JkShmFile /var/log/apache2/mod_jk.shm >> >> > (see later the copy of the file) >> >> > >> >> > Now I have different errors: >> >> > >> >> > [Sat Nov 18 09:27:57 2006] [16854:7072] [info] >> >> > ajp_send_request::jk_ajp_common.c (1170): (ajp13) socket 33 is not >> >> > connected any more (errno=11) >> >> > [Sat Nov 18 09:27:57 2006] [16854:7072] [info] >> >> > ajp_send_request::jk_ajp_common.c (1194): (ajp13) error sending >> >> > request. Will try another pooled connection >> >> > [Sat Nov 18 09:27:57 2006] [16854:7072] [info] >> >> > ajp_send_request::jk_ajp_common.c (1218): (ajp13) all endpoints are >> >> > disconnected or dead >> >> > [Sat Nov 18 09:27:57 2006] [16854:7072] [info] >> >> > ajp_service::jk_ajp_common.c (1867): (ajp13) sending request to >> tomcat >> >> > failed, recoverable operation attempt=1 >> >> > >> >> > What do they mean? >> >> > >> >> > I'm using versions >> >> > mod_jk/1.2.19 >> >> > Apache/2.0.54 >> >> > tomcat/5.5.20 >> >> > >> >> > >> >> > Thanks again!! >> >> > >> >> > Enrico >> >> > >> >> > >> >> > # =============================================================== >> >> > # mod_jk.conf >> >> > #### >> >> > # Load mod_jk module >> >> > LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so >> >> > # Declare the module for <IfModule directive> (remove this line on >> >> > Apache 2.0.x) >> >> > #AddModule mod_jk.c >> >> > # Where to find workers.properties >> >> > JkWorkersFile /etc/apache2/workers.properties >> >> > # Where to put jk logs >> >> > JkLogFile /var/log/apache2/mod_jk.log >> >> > >> >> > JkShmFile /var/log/apache2/mod_jk.shm >> >> > >> >> > >> >> > # Set the jk log level [debug/error/info] >> >> > JkLogLevel info >> >> > # Select the log format >> >> > JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " >> >> > # JkOptions indicate to send SSL KEY SIZE, >> >> > JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories >> >> > # JkRequestLogFormat set the request format >> >> > JkRequestLogFormat "%w %V %T" >> >> > # Send servlet for context /examples to worker named worker1 >> >> > #JkMount /examples/servlet/* worker1 >> >> > # Send JSPs for context /examples to worker named worker1 >> >> > >> >> > >> >> > #============== workers.properties ============================= >> >> > workers.tomcat_home=/tomcat/dir >> >> > workers.java_home=/opt/jdk >> >> > ps=/ >> >> > worker.list=ajp13 >> >> > worker.ajp12.port=8007 >> >> > worker.ajp12.host=localhost >> >> > worker.ajp12.type=ajp12 >> >> > worker.ajp12.lbfactor=1 >> >> > worker.ajp13.port=8009 >> >> > worker.ajp13.host=localhost >> >> > worker.ajp13.type=ajp13 >> >> > worker.ajp13.lbfactor=1 >> >> > #worker.ajp13.connection_pool_size >> >> > worker.loadbalancer.type=lb >> >> > worker.loadbalancer.balance_workers=ajp12, ajp13 >> >> > >> >> > worker.inprocess.type=jni >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On 17/11/06, Rainer Jung <[EMAIL PROTECTED]> wrote: >> >> >> Please give details on your mod_jk version and concerning your >> >> >> configuration (mod_jk config inside httpd.conf and >> >> workers.properties). >> >> >> >> >> >> Errno 2 looks line not such file or directory. So does >> >> >> /etc/apache2/logs/jk-runtime-status exist as a file and is the >> apache >> >> >> user allowed to write into it. Does the directory /etc/apache2/logs >> >> >> exist and again, does the apache user have write permissions there? >> >> >> >> >> >> Does the log message already show, when you are starting? If yes, >> >> could >> >> >> you reproduce with JkLogLevel trace and provide the resulting file? >> >> >> >> >> >> Regards, >> >> >> >> >> >> Rainer >> >> >> >> >> >> >> >> >> Enrico Donelli schrieb: >> >> >> > Hi all, >> >> >> > I'm having some problems with the mod_jk connector. >> >> >> > In mod_jk logs file I have a lot of lines like >> >> >> > >> >> >> > [Fri Nov 17 23:07:18 2006] [12236:7072] [error] >> >> >> > jk_child_init::mod_jk.c (2406): Attachning >> >> >> > shm:/etc/apache2/logs/jk-runtime-status errno=2 >> >> >> > >> >> >> > and from time to time the connector completely locks apache, >> forcing >> >> >> > me to restart both apache and tomcat. >> >> >> > >> >> >> > >> >> >> > Any idea? I could find no documentation about this error :(( >> >> >> > >> >> >> > I'm using debian3.1, jdk1.5.0_05 and tomcat 5.20. >> >> >> > >> >> >> > Thanks in advance!! >> >> >> > Enrico >> >> >> > >> >> > >> >> > >> --------------------------------------------------------------------- >> >> > To start a new topic, e-mail: users@tomcat.apache.org >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> --------------------------------------------------------------------- >> >> To start a new topic, e-mail: users@tomcat.apache.org >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
