Re: [OT] Anybody using Apache 2.0.59 and Tomcat 5.5.17 on Windows 2003
Hi, I am using Apache 2.0.59 and Tomcat 5.0.28 with mod_jk 1.2.20 on Windows 2003 SP1 but the system have some issue on the socket layer. In fact, after some time, some users are able to crash our architecture: apache answers to request such as *.html but mod_jk says it cannot connect to tomcat. Even a restart of services doesn't change anythink. Tomcat is running and answer for simple "hello world" jsp pages but cannot answer to /manage/html. I patch windows with KB 931311 and it seems to work properly. JNeuhoff wrote: > > Has anybody successfully managed to run Apache 2.0.59 and Tomcat 5.5.17 on > Windows 2003 on a real production server, and not just as a test system? > > We are still experiencing frequent TCP Connections Aborted errors (err=53) > for no apparent reasons, and because of that our live server becomes > unresponsive to clients and we end up re-booting our server machine once > or twice a week. > > (see http://www.nabble.com/mod_jk-replacement--tf3050993.html for more > details) > > This problem even occurs with firewall and anti-virus software all > switched off. > > Rainer Jung suggested to try out a Microsoft Hotfix > (http://support.microsoft.com/kb/925513) which we are still waiting for to > receive from Microsoft Technet, and once its there, we will try it out. > > J.Neuhoff > > -- View this message in context: http://www.nabble.com/Anybody-using-Apache-2.0.59-and-Tomcat-5.5.17-on-Windows-2003-tf3200025.html#a8887082 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] Apache mod_jk memory leak?
Hi, I am using Apache 2.0.59 and Tomcat 5.0.28 with mod_jk 1.2.20 on Windows 2003 SP1 but the system have some issue on the socket layer. In fact, after some time, some users are able to crash our architecture: apache answers to request such as *.html but mod_jk says it cannot connect to tomcat. Even a restart of services doesn't change anythink. Tomcat is running and answer for simple "hello world" jsp pages but cannot answer to /manage/html. I have exacltly the same error logs and thread dumps as you are. I patch windows with KB 931311 and it seems to work properly. JNeuhoff wrote: > > I have just managed to repeat the error. 2 of us, from 2 different > workstations, hammered our website for a minute, by rapidly clicking on > links within the same site before it ended up always responding with a > standard Error 503 (Service unavailable) coming from the Apache frontend. > I checked all the log files, and again the only errors recorded were found > in the mod_jk.log: > > > [Fri Jan 19 11:34:42 2007] [0404:2392] [info] mod_jk.c (2142): Service > error=0 for worker=ajp13 > [Fri Jan 19 11:34:42 2007] [0404:2388] [error] jk_ajp_common.c (948): > (ajp13) can't receive the response message from tomcat, network problems > or tomcat is down (127.0.0.1:8009), err=-53 > [Fri Jan 19 11:34:42 2007] [0404:2388] [error] jk_ajp_common.c (1566): > (ajp13) Tomcat is down or refused connection. No response has been sent to > the client (yet) > [Fri Jan 19 11:34:42 2007] [0404:2388] [info] jk_ajp_common.c (1877): > (ajp13) receiving from tomcat failed, recoverable operation attempt=1 > [Fri Jan 19 11:34:42 2007] [0404:2388] [info] jk_ajp_common.c (1916): > (ajp13) sending request to tomcat failed, recoverable operation attempt=2 > [Fri Jan 19 11:34:42 2007] [0404:2388] [error] jk_ajp_common.c (1928): > (ajp13) Connecting to tomcat failed. Tomcat is probably not started or is > listening on the wrong port > > > > The 2 connections between Apache and Tomcat according the the netstat -a > command just after the web server started the 503 (Service unavilable) > responses (hightlighted in bold): > > Proto Local Address Foreign AddressState > TCPDAOHPRW2:epmap DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:microsoft-ds DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:1078 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:3389 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:8009 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:8080 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:1 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:2093 DAOHPRW2.essex.ac.uk:8009 TIME_WAIT > TCPDAOHPRW2:2110 DAOHPRW2.essex.ac.uk:8009 TIME_WAIT > TCPDAOHPRW2:8005 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:netbios-ssn DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:2076 daohprp2.essex.ac.uk:3306 ESTABLISHED > TCPDAOHPRW2:2077 daohprp2.essex.ac.uk:microsoft-ds > TIME_WAIT > TCPDAOHPRW2:2176 sernt29.essex.ac.uk:epmap ESTABLISHED > TCPDAOHPRW2:2177 sernt29.essex.ac.uk:1025 ESTABLISHED > TCPDAOHPRW2:2181 sernt29.essex.ac.uk:microsoft-ds > TIME_WAIT > TCPDAOHPRW2:2194 sernt50.essex.ac.uk:epmap ESTABLISHED > TCPDAOHPRW2:2204 sernt5.essex.ac.uk:epmap ESTABLISHED > TCPDAOHPRW2:2215 sernt25.essex.ac.uk:epmap ESTABLISHED > TCPDAOHPRW2:2230 dalinux6a.essex.ac.uk:netbios-ssn > ESTABLISHED > TCPDAOHPRW2:2250 sernt2.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:2253 bodger.essex.ac.uk:microsoft-ds TIME_WAIT > TCPDAOHPRW2:http DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:http daohpr1.essex.ac.uk:1528 TIME_WAIT > TCPDAOHPRW2:http daohpr2.essex.ac.uk:1936 TIME_WAIT > TCPDAOHPRW2:netbios-ssn DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:2232 sernt23.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:2237 sernt9.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:2245 serlx08.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:2249 sernt2.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:2261 sernt23.essex.ac.uk:netbios-ssn TIME_WAIT > TCPDAOHPRW2:3389 daohpr1.essex.ac.uk:1533 ESTABLISHED > > > Half another later, long after the connection_pool_timeout, > connect_timeout and prepost_timeout, the netstat -a command still shows > this: > > Proto Local Address Foreign AddressState > TCPDAOHPRW2:epmap DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:microsoft-ds DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:1078 DAOHPRW2.essex.ac.uk:0 LISTENING > TCPDAOHPRW2:3389 DAOHPRW2.essex.ac.uk:0 LI
RE: Apache mod_jk memory leak?
Hi! I don't know IIS but maybe the patch could help. This is not an official patch. WindowsServer2003-KB931311 can be retrieved by calling microsoft support. But I can also send you the patch if you can't get it. Romain Per Johnsson wrote: > > Hi! > I wonder if this is the same problem we have, but we are using IIS6 and > isapi_redirect.dll and if I'm not totally wrong the same codebase is > used for apache and iis. > > We have come to the conclusion that there is a error in the "free > memory" causing a crash when the pool workers of the iis is unloaded, > unfortunaly we have not managed to see what is causing the error. > > Am I wrong or is this a Win 2003 Server error which can be helped with > the suggested patch. > > I wrote a longer mail about our problems: > > http://marc.theaimsgroup.com/?l=tomcat-user&m=117092232007880&w=2 > > > /Per Jonsson > > -Original Message- > From: RChartier [mailto:[EMAIL PROTECTED] > Sent: den 9 februari 2007 16:00 > To: users@tomcat.apache.org > Subject: Re: [OT] Apache mod_jk memory leak? > > > Hi, > > I am using Apache 2.0.59 and Tomcat 5.0.28 with mod_jk 1.2.20 on Windows > 2003 SP1 but the system have some issue on the socket layer. In fact, > after some time, some users are able to crash our architecture: apache > answers to request such as *.html but mod_jk says it cannot connect to > tomcat. Even a restart of services doesn't change anythink. Tomcat is > running and answer for simple "hello world" jsp pages but cannot answer > to /manage/html. > > I have exacltly the same error logs and thread dumps as you are. > > I patch windows with KB 931311 and it seems to work properly. > > > JNeuhoff wrote: >> >> I have just managed to repeat the error. 2 of us, from 2 different >> workstations, hammered our website for a minute, by rapidly clicking >> on links within the same site before it ended up always responding >> with a standard Error 503 (Service unavailable) coming from the Apache > frontend. >> I checked all the log files, and again the only errors recorded were >> found in the mod_jk.log: >> >> >> [Fri Jan 19 11:34:42 2007] [0404:2392] [info] mod_jk.c (2142): >> Service error=0 for worker=ajp13 [Fri Jan 19 11:34:42 2007] >> [0404:2388] [error] jk_ajp_common.c (948): >> (ajp13) can't receive the response message from tomcat, network >> problems or tomcat is down (127.0.0.1:8009), err=-53 [Fri Jan 19 >> 11:34:42 2007] [0404:2388] [error] jk_ajp_common.c (1566): >> (ajp13) Tomcat is down or refused connection. No response has been >> sent to the client (yet) [Fri Jan 19 11:34:42 2007] [0404:2388] [info] > >> jk_ajp_common.c (1877): >> (ajp13) receiving from tomcat failed, recoverable operation attempt=1 >> [Fri Jan 19 11:34:42 2007] [0404:2388] [info] jk_ajp_common.c (1916): >> (ajp13) sending request to tomcat failed, recoverable operation >> attempt=2 [Fri Jan 19 11:34:42 2007] [0404:2388] [error] > jk_ajp_common.c (1928): >> (ajp13) Connecting to tomcat failed. Tomcat is probably not started or > >> is listening on the wrong port >> >> >> The 2 connections between Apache and Tomcat according the the netstat >> -a command just after the web server started the 503 (Service >> unavilable) responses (hightlighted in bold): >> >> Proto Local Address Foreign AddressState >> TCPDAOHPRW2:epmap DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:microsoft-ds DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:1078 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:3389 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:8009 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:8080 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:1 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:2093 DAOHPRW2.essex.ac.uk:8009 TIME_WAIT >> TCPDAOHPRW2:2110 DAOHPRW2.essex.ac.uk:8009 TIME_WAIT >> TCPDAOHPRW2:8005 DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:netbios-ssn DAOHPRW2.essex.ac.uk:0 LISTENING >> TCPDAOHPRW2:2076 daohprp2.essex.ac.uk:3306 ESTABLISHED >> TCPDAOHPRW2:2077 daohprp2.essex.ac.uk:microsoft-ds >> TIME_WAIT >> TCPDAOHPRW2:2176 sernt29.essex.ac.uk:epmap ESTABLISHED >> TCPDAOHPRW2:2177 sernt29.essex.ac.uk:1025 ESTABLISHED >> TCPDAOHPRW2:2181 sernt29.essex.ac.uk:microsoft-ds >> TIME_WAIT
