Hi, First step in debugging this type of issue: take Apache and the connectors out of the equation. Run tomcat standalone and see if the issue still persists. My guess would be not.
You're barking up the wrong tree completely when you think this is a Tomcat limitation. Tomcat instances routinely handle thousands of connections and millions of hits per day. How much of that is concurrent depends on your webapp and hardware of course. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Ercan, Tolga [mailto:[EMAIL PROTECTED] >Sent: Monday, September 20, 2004 9:24 PM >To: [EMAIL PROTECTED] >Subject: Tomcat Hanging... > >I'm currently trying to deploy tomcat and we're having a problem with >tomcat appearing to hang. Here's the environment: > > > >Apache 1.3.19 > >Mod_jk > >Tomcat 5.0.27 > > > >We have 5 apache servers, connecting to 2 tomcat workers via mod_jk. >These tomcat workers are load balanced via JK, and we've clustered the >two instances. What we're seeing is the environment work for about 5 >minutes. During that time, the number of open connections to either >tomcat instance steadily increases to 250+. When we reach that >threshold, mod_jk log starts to report the following errors for both >workers: > > > >[Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1024)]: Error connecting >to the Tomcat process. > >[Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1468)]: sending request to >tomcat failed in send loop. err=1 > >[Fri Sep 10 16:43:21 2004] [jk_connect.c (188)]: jk_open_socket, >connect() failed errno = 145 > >[Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (720)]: Error connecting to >tomcat. Tomcat is probably not started or is listening on the wrong >host/port (xx.xx.xx.xx:8030). Failed errno = 145 > >[Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1024)]: Error connecting >to the Tomcat process. > >[Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1468)]: sending request to >tomcat failed in send loop. err=2 > >[Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1477)]: Error connecting >to tomcat. Tomcat is probably not started or is listening on the wrong >port. worker=worker1 failed errno = 145 > > > >The tomcat servers (worker1, worker2) are both up, and listening on port >8030 but at this point, the application appears to hang. My questions >are: > > > >1) Should there be this many open connections? Is having this many >connections open create problems communicating with tomcat? > >2) Is this a known issue? I haven't seen anyone else report the >problem, so I'm assuming no... > >3) Is this a tomcat performance issue? What are the performance >limitations of tomcat? Or am I barking up the wrong tree in thinking >this is a tomcat performance issue? > > > >Thanks! > >~t This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
