This looks like Bug 4599: <http://nagoya.betaversion.org/bugzilla/show_bug.cgi?id=4599>
To fix, you will need to patch your Tomcat 3.3's ThreadPool class or try the nightly Tomcat 3.3.1 at: <http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/> If you want to try patching 3.3, the only change to ThreadPool.java since 3.3's release is this fix. You can use the file found at: <http://cvs.apache.org/viewcvs/jakarta-tomcat/src/share/org/apache/tomcat/util/threads/ThreadPool.java> Revision 1.8 is the one you want. Cheers, Larry > -----Original Message----- > From: Adrian Erimescu [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 2:30 PM > To: Tomcat Users List > Subject: Big problem > > > > Hi, > > I'm using tomcat 3.3-3 (rpm packages tomcat-3.3-3 and > tomcat-mod-3.3-1) on a linux machine (RedHat 7.1, recompiled > apache 1.3.22 with php 4.1.1, IBM Java 2.13). The server is > running only one site and has permanently around 260 apache > threads started (~250.000 hits per day). > In Apache MaxClients is 512 and in server.xml the ajp13 > connector is set with maxThreads="512", maxSpareThreads="50", > minSpareThreads="10", thread_pool="on". > > The big problem is that periodically, I get this messages on > mod_jk.log: > > [Fri Jan 04 02:19:46 2002] [jk_ajp13_worker.c (228)]: > connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed > [Fri Jan 04 02:19:46 2002] [jk_ajp13_worker.c (712)]: Error > reading reply > [Fri Jan 04 02:19:46 2002] [jk_ajp13_worker.c (845)]: In > jk_endpoint_t::service, get_reply failed in send loop 0 > [Fri Jan 04 02:23:28 2002] [jk_connect.c (143)]: > jk_open_socket, connect() failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (196)]: In > jk_endpoint_t::connect_to_tomcat, failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (635)]: Error > connecting to the Tomcat process. > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (848)]: In > jk_endpoint_t::service, send_request failed in send loop 0 > [Fri Jan 04 02:23:28 2002] [jk_connect.c (143)]: > jk_open_socket, connect() failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (196)]: In > jk_endpoint_t::connect_to_tomcat, failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (635)]: Error > connecting to the Tomcat process. > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (848)]: In > jk_endpoint_t::service, send_request failed in send loop 1 > [Fri Jan 04 02:23:28 2002] [jk_connect.c (143)]: > jk_open_socket, connect() failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (196)]: In > jk_endpoint_t::connect_to_tomcat, failed errno = 111 > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (635)]: Error > connecting to the Tomcat process. > [Fri Jan 04 02:23:28 2002] [jk_ajp13_worker.c (848)]: In > jk_endpoint_t::service, send_request failed in send loop 2 > .... > (The messages repeat for thousends of times) > > Sometimes, the connection to Tomcat is regain and everything > is working fine, but every time after ~24 hours the messages > reappear and the servlets are no longer executed without any > other chance to work again but restarting Tomcat. Even when I > try to stop tomcat, some processes remain active and will not > be killed anyway but 'killall java'. > > I read lots of messages on Tomcat mailing lists and forums > but I can't get this problem right. > > Any help would be appreciated. > > Regards, > > Adrian Erimescu > REALMEDIA ROMANIA > ................................... > http://www.realmedia.ro > Tel/Fax: +40 56 195294 > ICQ#: 39233687 > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
