Re: 10 connection limit with IIS and JK/ISAPI 1.2.14
src="http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html";> Cachesize defines the number of connections made to the AJP backend that are maintained as a connection pool. It will limit the number of those connection that each web server child process can made. Cachesize property is used only for multi threaded web servers such as Apache 2.0 (worker), IIS and Netscape. The cachesize property should reflect the number of threads per child process. JK will discover the number of threads per child process on Apache 2 web server with worker-mpm and set its default value to match the ThreadsPerChild Apache directive. For IIS the default value is 10. For other web servers this value has to be set manually. Do not use cachesize with values higher then 1 on Apache 2.x prefork or Apache 1.3.x! Spors, Jeffrey R wrote: I also ran into this just today (although I don't get entries in my logs). I believe I found a solution. In workers.properties under the ajp13 Worker Definition I uncommented the worker.ajp13.cachesize line and set it equal to the desired max cache size. For example: worker.ajp13.cachesize=20 I don't really know the details of how jk works so I don't know what implications setting this value has. If there are any, please let me know. Hope this helps. Jeff Spors Winona State University -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="443" debug="5" connectionTimeout="2" protocol="AJP/1.3"/> Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - To
RE: 10 connection limit with IIS and JK/ISAPI 1.2.14
I bet that's it. In looking at my workers.properties files, I neglected to prefix my settings with the name of the worker. I might be retarded;) >>> [EMAIL PROTECTED] 12:36:27 PM 8/25/2005 >>> I also ran into this just today (although I don't get entries in my logs). I believe I found a solution. In workers.properties under the ajp13 Worker Definition I uncommented the worker.ajp13.cachesize line and set it equal to the desired max cache size. For example: worker.ajp13.cachesize=20 I don't really know the details of how jk works so I don't know what implications setting this value has. If there are any, please let me know. Hope this helps. Jeff Spors Winona State University -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 10 connection limit with IIS and JK/ISAPI 1.2.14
I also ran into this just today (although I don't get entries in my logs). I believe I found a solution. In workers.properties under the ajp13 Worker Definition I uncommented the worker.ajp13.cachesize line and set it equal to the desired max cache size. For example: worker.ajp13.cachesize=20 I don't really know the details of how jk works so I don't know what implications setting this value has. If there are any, please let me know. Hope this helps. Jeff Spors Winona State University -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 10 connection limit with IIS and JK/ISAPI 1.2.14
Ok. Sorry, I tried the easy answer, sometimes you get lucky :) Beyond that I'm afraid I can't think of anything off the top of my head. Frank On Wed, August 24, 2005 4:38 pm, David Boyer said: > This is our main public web server. We routinely have more than 10 > connections. The limit we're hitting seems only to affect the connection > between IIS and Tomcat. > > I don't think IIS 6 has the same slider as IIS 5 did for this. However, I > have verified that I have connection limits set to 'unlimited' at both the > global and site levels. > > - Original Message - > From: "Frank W. Zammetti" <[EMAIL PROTECTED]> > To: "Tomcat Users List" > Cc: "Tomcat Users List" > Sent: Wednesday, August 24, 2005 3:31 PM > Subject: Re: 10 connection limit with IIS and JK/ISAPI 1.2.14 > > >> If memory serves, IIS defaults to a 10 connection maximum. You need to >> go >> into the admin console and move the pretty slider over :) >> >> Also if memory serves, there is a hard 10 connection limit for the >> non-server versions, but that doesn't apply here apparently. >> >> -- >> Frank W. Zammetti >> Founder and Chief Software Architect >> Omnytex Technologies >> http://www.omnytex.com >> >> On Wed, August 24, 2005 4:28 pm, David Boyer said: >>> is is fairly common with non-server version of IIS, but that's by >>> design. >>> I'm using Windows Server 2003 Enterprise. Thanks. >>> >>> - Original Message - >>> From: "Jay Burgess" <[EMAIL PROTECTED]> >>> To: >>> Sent: Wednesday, August 24, 2005 3:19 PM >>> Subject: RE: 10 connection limit with IIS and JK/ISAPI 1.2.14 >>> >>> >>>>I don't really have an answer for you, but Google'ing "iis 10 >>>> connection >>>>limit" >>>> returns a lot of hits. It looks like a fairly common question/issue. >>>> Maybe >>>> it'll help. >>>> >>>> Jay >>>> >>>> | Jay Burgess [Vertical Technology Group] >>>> | "Essential Technology Links" >>>> | http://www.vtgroup.com/ >>>> >>>> >>>> >>>> -Original Message- >>>> From: David [mailto:[EMAIL PROTECTED] >>>> Sent: Wednesday, August 24, 2005 3:09 PM >>>> To: tomcat-user@jakarta.apache.org >>>> Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 >>>> >>>> I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, >>>> with >>>> the >>>> JK 1.2.14 isapi_redirector.dll. >>>> >>>> I've been trying to track down a problem whereby all of the web apps >>>> under >>>> our >>>> Tomcat instance are seeming to stall. There's no indication of any >>>> problems in >>>> the Tomcat logs themselves. I suspect IIS is unable to forward >>>> requests >>>> to >>>> Tomcat. I either have to recycle the IIS worker process or restart >>>> Tomcat >>>> to >>>> resolve the problem. >>>> >>>> Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): >>>> >>>> Z:\>netstat -a -n | grep 8008 >>>> TCP0.0.0.0:8008 0.0.0.0:0 LISTENING >>>> TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED >>>> TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED >>>> TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED >>>> TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED >>>> TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED >>>> TCP147.92.2.137:8
Re: 10 connection limit with IIS and JK/ISAPI 1.2.14
This is our main public web server. We routinely have more than 10 connections. The limit we're hitting seems only to affect the connection between IIS and Tomcat. I don't think IIS 6 has the same slider as IIS 5 did for this. However, I have verified that I have connection limits set to 'unlimited' at both the global and site levels. - Original Message - From: "Frank W. Zammetti" <[EMAIL PROTECTED]> To: "Tomcat Users List" Cc: "Tomcat Users List" Sent: Wednesday, August 24, 2005 3:31 PM Subject: Re: 10 connection limit with IIS and JK/ISAPI 1.2.14 If memory serves, IIS defaults to a 10 connection maximum. You need to go into the admin console and move the pretty slider over :) Also if memory serves, there is a hard 10 connection limit for the non-server versions, but that doesn't apply here apparently. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, August 24, 2005 4:28 pm, David Boyer said: is is fairly common with non-server version of IIS, but that's by design. I'm using Windows Server 2003 Enterprise. Thanks. - Original Message - From: "Jay Burgess" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 24, 2005 3:19 PM Subject: RE: 10 connection limit with IIS and JK/ISAPI 1.2.14 I don't really have an answer for you, but Google'ing "iis 10 connection limit" returns a lot of hits. It looks like a fairly common question/issue. Maybe it'll help. Jay | Jay Burgess [Vertical Technology Group] | "Essential Technology Links" | http://www.vtgroup.com/ -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - To unsubscribe, e
Re: 10 connection limit with IIS and JK/ISAPI 1.2.14
If memory serves, IIS defaults to a 10 connection maximum. You need to go into the admin console and move the pretty slider over :) Also if memory serves, there is a hard 10 connection limit for the non-server versions, but that doesn't apply here apparently. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, August 24, 2005 4:28 pm, David Boyer said: > is is fairly common with non-server version of IIS, but that's by design. > I'm using Windows Server 2003 Enterprise. Thanks. > > - Original Message - > From: "Jay Burgess" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, August 24, 2005 3:19 PM > Subject: RE: 10 connection limit with IIS and JK/ISAPI 1.2.14 > > >>I don't really have an answer for you, but Google'ing "iis 10 connection >>limit" >> returns a lot of hits. It looks like a fairly common question/issue. >> Maybe >> it'll help. >> >> Jay >> >> | Jay Burgess [Vertical Technology Group] >> | "Essential Technology Links" >> | http://www.vtgroup.com/ >> >> >> >> -----Original Message----- >> From: David [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, August 24, 2005 3:09 PM >> To: tomcat-user@jakarta.apache.org >> Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 >> >> I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, >> with >> the >> JK 1.2.14 isapi_redirector.dll. >> >> I've been trying to track down a problem whereby all of the web apps >> under >> our >> Tomcat instance are seeming to stall. There's no indication of any >> problems in >> the Tomcat logs themselves. I suspect IIS is unable to forward requests >> to >> Tomcat. I either have to recycle the IIS worker process or restart >> Tomcat >> to >> resolve the problem. >> >> Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): >> >> Z:\>netstat -a -n | grep 8008 >> TCP0.0.0.0:8008 0.0.0.0:0 LISTENING >> TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED >> TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED >> >> Every time the stall has happened, I have noticed that there are always >> exactly >> ten connetions between IIS and Tomcat (they're on the same server). >> Everything >> works fine until we reach this point. >> >> In my JK log, I'm seeing things like this: >> >> [Wed Aug 24 14:10:57 2005] [error] >> ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the >> response message from tomcat, network problems or tomcat is down >> (147.92.2.137:8008), err=-54 >> [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c >> (1503): >> Tomcat >> is down or refused connection. No response has been sent to the client >> (yet) >> >> >> My workers.properties looks like this: >> >> worker.list=ajp13a >> >> worker.ajp13a.port=8008 >> worker.ajp13a.host=www.bvu.edu >> worker.ajp13a.type=ajp13 >> >> cachesize=20 >> cache_timeout=600 >> recycle_timeout=300 >> >> >> And here's the AJP connection defininition from my server.xml: >> >&
Re: 10 connection limit with IIS and JK/ISAPI 1.2.14
is is fairly common with non-server version of IIS, but that's by design. I'm using Windows Server 2003 Enterprise. Thanks. - Original Message - From: "Jay Burgess" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 24, 2005 3:19 PM Subject: RE: 10 connection limit with IIS and JK/ISAPI 1.2.14 I don't really have an answer for you, but Google'ing "iis 10 connection limit" returns a lot of hits. It looks like a fairly common question/issue. Maybe it'll help. Jay | Jay Burgess [Vertical Technology Group] | "Essential Technology Links" | http://www.vtgroup.com/ -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - 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]
RE: 10 connection limit with IIS and JK/ISAPI 1.2.14
I don't really have an answer for you, but Google'ing "iis 10 connection limit" returns a lot of hits. It looks like a fairly common question/issue. Maybe it'll help. Jay | Jay Burgess [Vertical Technology Group] | "Essential Technology Links" | http://www.vtgroup.com/ -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 3:09 PM To: tomcat-user@jakarta.apache.org Subject: 10 connection limit with IIS and JK/ISAPI 1.2.14 I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
10 connection limit with IIS and JK/ISAPI 1.2.14
I'm using Tomcat 5.5.9 on Windows Server 2003, JDK 1.5.0_04, IIS 6.0, with the JK 1.2.14 isapi_redirector.dll. I've been trying to track down a problem whereby all of the web apps under our Tomcat instance are seeming to stall. There's no indication of any problems in the Tomcat logs themselves. I suspect IIS is unable to forward requests to Tomcat. I either have to recycle the IIS worker process or restart Tomcat to resolve the problem. Here's what I'm seeing with netstat (port 8008 is my AJP 1.3 port): Z:\>netstat -a -n | grep 8008 TCP0.0.0.0:8008 0.0.0.0:0 LISTENING TCP147.92.2.137:2871 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2915 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2944 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2965 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:2969 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3019 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3034 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3039 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3041 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:3060 147.92.2.137:8008 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2871 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2915 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2944 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2965 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:2969 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3019 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3034 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3039 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3041 ESTABLISHED TCP147.92.2.137:8008 147.92.2.137:3060 ESTABLISHED Every time the stall has happened, I have noticed that there are always exactly ten connetions between IIS and Tomcat (they're on the same server). Everything works fine until we reach this point. In my JK log, I'm seeing things like this: [Wed Aug 24 14:10:57 2005] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (147.92.2.137:8008), err=-54 [Wed Aug 24 14:10:57 2005] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) My workers.properties looks like this: worker.list=ajp13a worker.ajp13a.port=8008 worker.ajp13a.host=www.bvu.edu worker.ajp13a.type=ajp13 cachesize=20 cache_timeout=600 recycle_timeout=300 And here's the AJP connection defininition from my server.xml: Any idea what might be happening? It sure looks like I'm hitting some kind of 10 connection limit somewhere, but I can't seem to figure out where.
