DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17342>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17342 Tomcat JK2 connection refreshes causes Apache to return error 500 Summary: Tomcat JK2 connection refreshes causes Apache to return error 500 Product: Tomcat 4 Version: 4.1.18 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] With Tomcat JK2 connectionTimeout set, mod_jk is retries three times while the connections are being reset. On a very fast machine mod_jk retries before a new connection is available and returns an error 500 to the end user. The workaround is to set connectionTimeout to -1 to stop connection refreshes. There now follows an EMail conversation between myself and Costin on this problem: I think: >From winsock.h: #define WSABASEERR 10000 #define WSAECONNABORTED (WSABASEERR+53) >From VC.NET help files: WSAECONNABORTED=The virtual circuit was terminated due to a time-out or other failure. The application should close the socket as it is no longer usable. Dave. > Thanks Dave. > > Now if someone has windows and can grep what errno "53" means... > > > Costin > > Oxley, David wrote: > >> Costin, >> >> Here is the log produced with mod_jk HEAD: >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (681)]: ERROR: can't >> receive the response message from tomcat, network problems or tomcat >> is down. err=-53 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1051)]: Error reading >> reply >> from tomcat. Tomcat is down or network problems. >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1188)]: ERROR: Receiving >> [from >> tomcat failed, recoverable operation. err=0 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (681)]: ERROR: can't >> receive >> the response message from tomcat, network problems or tomcat is down. >> err=-1 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1051)]: Error reading >> reply >> from tomcat. Tomcat is down or network problems. >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1188)]: ERROR: Receiving >> [from >> tomcat failed, recoverable operation. err=1 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (681)]: ERROR: can't >> receive >> the response message from tomcat, network problems or tomcat is down. >> err=-1 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1051)]: Error reading >> reply >> from tomcat. Tomcat is down or network problems. >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1188)]: ERROR: Receiving >> [from >> tomcat failed, recoverable operation. err=2 >> [Mon Feb 17 17:23:26 2003] [jk_ajp_common.c (1199)]: Error connecting >> to >> tomcat. Tomcat is probably not started or is listenning on the wrong >> port. >> Failed errno = 53 >> >> Cheers. >> Dave. >> >>> -----Original Message----- >>> From: Oxley, David [mailto:[EMAIL PROTECTED] >>> Sent: 17 February 2003 17:00 >>> To: 'Tomcat Developers List' >>> Subject: RE: mod_jk and Apache timeouts? >>> >>> Costin, >>> >>> I will rebuild from HEAD now and give it a try. >>> But I think I may have sorted found the problem. I have changed the >>> Connector timeout to -1 in server.xml, and error 500's is no longer >>> returned. Therefore on this box, mod_jk is too quick for Tomcat (I >>> think). mod_jk tries to connect and fails 3 times (before TC has >>> restarted its Connector threads) and returns an error 500 to the >>> client. >>> >>> Dave. >>> >>> > -----Original Message----- >>> > From: Costin Manolache [mailto:[EMAIL PROTECTED] >>> > Sent: 17 February 2003 17:02 >>> > To: [EMAIL PROTECTED] >>> > Subject: Re: mod_jk and Apache timeouts? >>> > >>> > I suspect it's a windows specific return code from recv(). >>> > >>> > The code in question calls socket_recvfull - which in turn calls >>> recv() >>> > to fill a buffer. It handles EAGAIN - but knowing windows, it may >>> > be something else. >>> > >>> > If you can do a checkout from HEAD and built again - you should >>> > see the errno at the end of the message, so we can figure out what >>> happens. >>> > >>> > The first error is the one that matters - the others are just jk >>> doing >>> > a retry. The message is bad - err=0,1,2 should be "retry=0,1,2" >>> > >>> > >>> > >>> > Costin >>> > >>> > >>> > Oxley, David wrote: >>> > >>> > > I have some strange error messages in mod_jk.log that I cannot >>> explain, >>> > > and that I need to resolve urgently. >>> > > >>> > > Server: >>> > > Dual Xeon 2.5Ghz server. >>> > > Windows 2000 Professional SP3 >>> > > Apache 2.0.44 >>> > > Tomcat 4.1.18 >>> > > Mod_jk 1.2.2 >>> > > >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (681)]: ERROR: >>> > > can't >>> > receive >>> > > the response message from tomcat, network problems or tomcat is >>> down. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1050)]: Error >>> > > reading >>> > reply >>> > > from tomcat. Tomcat is down or network problems. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1187)]: ERROR: >>> > > [Receiving from tomcat failed, recoverable operation. err=0 >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (681)]: ERROR: can't >>> > receive >>> > > the response message from tomcat, network problems or tomcat is >>> down. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1050)]: Error >>> > > reading >>> > reply >>> > > from tomcat. Tomcat is down or network problems. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1187)]: ERROR: >>> > > [Receiving from tomcat failed, recoverable operation. err=1 >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (681)]: ERROR: can't >>> > receive >>> > > the response message from tomcat, network problems or tomcat is >>> down. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1050)]: Error >>> > > reading >>> > reply >>> > > from tomcat. Tomcat is down or network problems. >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1187)]: ERROR: >>> > > [Receiving from tomcat failed, recoverable operation. err=2 >>> > > [Mon Feb 17 14:49:38 2003] [jk_ajp_common.c (1198)]: Error >>> > > [connecting >>> > to >>> > > tomcat. Tomcat is probably not started or is listenning on the >>> wrong >>> > port. >>> > > Failed errno = 0 >>> > > >>> > > >>> > > >>> > > The line 'ERROR: Receiving from tomcat failed, recoverable >>> operation. >>> > > err=0' happens all the time but when the above happens i.e. >>> > > err=0 >>> -> >>> > err=1 >>> > > -> err=2 the browser is returned an error 500. I have a much >>> > > -> slower >>> box >>> > > (P4 1.7Ghz) that gets the err=0 line all the time but never gets >>> the >>> > err=1 >>> > > and err=2 lines and therefore never responds with an error 500. >>> > > >>> > > I have a feeling that there is a retry that is happening but the >>> box >>> is >>> > so >>> > > quick the threads on the Tomcat side aren't refreshed before >>> > > Apache >>> > gives >>> > > up. If this can be fixed by changing the config files then I >>> > > think >>> this >>> > > should be noted in the docs otherwise this is a bug!?!? >>> > > >>> > > >>> > > >>> > > Here is the relevant parts of the config. >>> > > >>> > > Server.xml: >>> > > >>> > > <Connector >>> className="org.apache.coyote.tomcat4.CoyoteConnector" >>> > > >>> > > port="8009" minProcessors="5" maxProcessors="75" >>> > > >>> > > enableLookups="true" redirectPort="443" >>> > > >>> > > acceptCount="10" debug="0" >>> > > connectionTimeout="20000" >>> > > >>> > > useURIValidationHack="false" >>> > > >>> > > >>> > > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/ >>> > > > >>> > > >>> > > workers.properties: >>> > > >>> > > worker.ajp13.port=8009 >>> > > >>> > > worker.ajp13.host=localhost >>> > > >>> > > worker.ajp13.type=ajp13 >>> > > >>> > > worker.ajp13.lbfactor=1 >>> > > >>> > > worker.ajp13.cachesize=10 >>> > > >>> > > worker.ajp13.cache_timeout=600 >>> > > >>> > > >>> > > >>> > > Thanks for your help. >>> > > >>> > > >>> > > >>> > > Dave Oxley >>> > > Development Team Leader >>> > > >>> > > Workplace Systems Plc >>> > > * +44 (0)118 9515 755 >>> > > * <mailto:[EMAIL PROTECTED]> >>> > > [EMAIL PROTECTED] >>> > > * <http://www.workplace-systems.plc.uk/> >>> > > http://www.workplace-systems.plc.uk >>> > > >>> > > >>> > > >>> > > There was once a young man who, in his youth, professed his >>> > > desire >>> to >>> > > become a great writer. >>> > > When asked to define great, he said, "I want to write stuff that >>> the >>> > whole >>> > > world will read, stuff that people will react to on a truly >>> emotional >>> > > level, stuff that will make them scream, cry, howl in pain and >>> > > anger!" He now works for Microsoft writing error messages. >>> > > >>> > > >>> > > >>> > > Workplace Systems plc, Precedent Drive, Rooksley, Milton Keynes, >>> MK13 >>> > 8PP. >>> > > Registered in England No. 2016236 >>> > > >>> > > Unless expressly stated the views expressed in this email may >>> > > not >>> be >>> the >>> > > views of Workplace Systems plc and the company, its directors, >>> officers >>> > or >>> > > employees accept no liability for its contents. Unless expressly >>> stated >>> > no >>> > > contracts may be concluded on behalf of Workplace Systems plc by >>> > > means >>> > of >>> > > e-mail communication. >>> > > >>> > > This e-mail, and any attachments are strictly confidential and >>> intended >>> > > for the addressee(s) only. If they have come to you in error you >>> must >>> > take >>> > > no action based on the contents, nor may you copy or show them >>> > > to >>> > anyone. >>> > > Please notify the sender of the error by return email. Please >>> ensure >>> you >>> > > have adequate virus protection before you open or detach any >>> > > documents from this transmission. Workplace Systems plc does not >>> > > accept any liability for viruses. >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> ____________________________________________________________________ >>> ____ >>> > > This e-mail has been scanned for all viruses by Star Internet. >>> > > The service is powered by MessageLabs. For more information on a >>> > > proactive anti-virus service working around the clock, around >>> > > the globe, visit: http://www.star.net.uk >>> > > >>> ____________________________________________________________________ >>> ____ >>> > >>> > >>> > >>> > ------------------------------------------------------------------ >>> > --- >>> > To unsubscribe, e-mail: [EMAIL PROTECTED] >>> > For additional commands, e-mail: [EMAIL PROTECTED] >>> > >>> > >>> > > ______________________________________________________________________ > __ >>> > This e-mail has been scanned for all viruses by Star Internet. The >>> > service is powered by MessageLabs. For more information on a >>> proactive >>> > anti-virus service working around the clock, around the globe, >>> > visit: http://www.star.net.uk >>> > > ______________________________________________________________________ > __ >>> >>> >>> ____________________________________________________________________ >>> ____ >>> This e-mail has been scanned for all viruses by Star Internet. The >>> service is powered by MessageLabs. For more information on a proactive >>> anti-virus service working around the clock, around the globe, visit: >>> http://www.star.net.uk >>> ________________________________________________________________________ >> >> >> _____________________________________________________________________ >> ___ >> This e-mail has been scanned for all viruses by Star Internet. The >> service is powered by MessageLabs. For more information on a proactive >> anti-virus service working around the clock, around the globe, visit: >> http://www.star.net.uk >> ________________________________________________________________________ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ______________________________________________________________________ > __ > This e-mail has been scanned for all viruses by Star Internet. The > service is powered by MessageLabs. For more information on a proactive > anti-virus service working around the clock, around the globe, visit: > http://www.star.net.uk > ________________________________________________________________________ > ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
