Travis take a look at this excerpt from Tomcat committer Mladen Turk.. "Just like Apache Web server for Windows, Microsoft IIS maintains a separate child process and thread pool for serving concurrent client connections. For non server products like Windows 2000 Professional or Windows XP the number of concurrent connections is limited to 10. This mean that you can not use workstation products for production servers unless the 10 connections limit will fulfil your needs. The server range of products does not impose that 10 connection limit, but just like Apache, the 2000 connections is a limit when the thread context switching will take its share and slow down the effective number of concurrent connections. If you need higher load you will need to deploy additional web servers and use Windows Network Load Balancer (WNLB) in front of Tomcat servers. "
http://people.apache.org/~mturk/docs/article/ftwai.html this means that Windows 2000 Pro or Windows XP has an artificial limit of 10..2 solutions another (more capable) OS existing OS with WindowsNetworkLoadBalancer Nota Bene: Any diagnosis is incomplete without looking at Java Thread Dumps as Rainier suggested earlier.. Martin- ----- Original Message ----- From: "Rainer Jung" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Friday, December 14, 2007 12:20 PM Subject: Re: Tomcat and IIS losing their link > Travis Haagen wrote: > > Hello, > > > > I've got IIS 6.0 linked with Tomcat 5.5.25 (with JDK 1.5.0_14-b03 and > > AJP dll) via the ISAPI connector (JK 1.2.25) on Windows 2003 Server, > > and during high traffic periods, the connection between IIS and > > Tomcat is being severed. This has been occurring in the mid-afternoon > > every day since this server went live and to get it running again, > > I've had to restart Tomcat. The peak connections to IIS during one of > > the days was just under 100, so this isn't really all that high of > > traffic. > > > > The isapi_redirect.log isn't much help. It has only been logging > > errors after the connection to Tomcat has been broken. Tomcat itself > > hasn't logged anything of relevance and I don't actually think that > > Tomcat is affected when the link is broken, but as I mentioned > > earlier, I have to restart Tomcat to get it to reconnect with IIS. > > Nevertheless at least i would be curious to know, what the exact > contents of the isapi redirector log files are. We don't need all of it, > but the first 100 lines or so could be interesting. What's you log level? > > Have a look at the other thread running on this list the last few days > ("ISAPI JK2 ran better than JK, how can that be?"). To get a slightly > better idea what's happening when, you could also introduce a load > balancer and a status worker. > > Most likely it would help to take Java Thread Dumps and look inside the > JVM, what your request threads are doing, when IIS gets stuck. > > Regards, > > Rainer > > --------------------------------------------------------------------- > 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]
