Hi, I recently moved one of our servers to RH 8.0. In the same step I also tried to move the affected application to Tomcat 4.1.18, working together with Apache 2.0.40 by using mod_jk 1.2.2. Everything went fine except that after about a day, Tomcat seems to have problems. The effects were:
- OutOfMemory Exceptions - No more responds from Tomcat - Error 500's The effects changed as I was trying different versions of Apache JDK and JK versions etc., but it seems to me that these results are caused by always the same problem: The connections between Apache and Tomcat seem to be created once, not used again and not destroyed anymore resulting in a huge amount of hanging threads, filling up memory etc. It usually took about a day until the problem occurred, but of course, this depends on the number of requests, amount of memory and the application itself. Currently, I'm trying JDK 1.3.1_07. Will see if it fixes the problem. Someone mentioned that before in this mailinglist. Typical log outputs of JkCoyoteHandler: . . [INFO] ChannelSocket - -Server has been restarted or reset this connection [INFO] ChannelSocket - -connection timeout reached . . and corresponding to that by mod_jk: . . [Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1050)]: Error reading reply from tomcat. Tomcat is down or network problems. [Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Fri Mar 21 01:13:50 2003] [jk_ajp_common.c (681)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. . . Regards, Daniel > -----Original Message----- > From: Marion McKelvie [mailto:[EMAIL PROTECTED] > Sent: Freitag, 21. März 2003 10:58 > To: Tomcat Users List > Subject: RE: Problems with tomcat 4.0.1 and 4.1.18 > > > Daniel > > Are you running in standalone mode or with a web server? > > I have seen a similar problem when using 4.1.18, but I think I've > traced it > to Apache 4.0.43 and mod_jk : Apache seems to keep producing > child processes > each of which uses up a mod_jk thread until I get the same error in > catalina.out > > Marion > > -----Original Message----- > From: Daniel Rubio [mailto:[EMAIL PROTECTED] > Sent: 21 March 2003 08:49 > To: [EMAIL PROTECTED] > Subject: Problems with tomcat 4.0.1 and 4.1.18 > > > Hi to all > > Recently, we updated our Tomcat server from 4.0.1 to 4.1.18. > All was perfect on the first day, but then the new server crashed and I > can't found the cause. > > Doing a ps -ef i see lots of tomcat processes that are'nt finalizing, > and when this number arrives to the value we have in acceptCount > variable it stops serving pages. > > Here is the error on catalina.out > > Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log > INFO: All threads are busy, waiting. Please increase maxThreads or check > the servlet status75 75 > > maxThreads is set to 75 but we haven't more from 2-3 concurrent users so > I think this is not th problem. > > We tried to run again the old server, but now we have a very strange > error, we can execute servlets but not jsp pages. Here is the error > received by the browser: > > Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently > unavailable > > this happens too to the examples directory, I think it's not caused by > the application... > > I'm going crazy, somebody could help? > > Thanks in advance > -- > ******************************************************** > Daniel Rubio Rodríguez > OASI (Organisme Autònom Per la Societat de la Informació) > c/ Assalt, 12 > 43003 - Tarragona > Tef.: 977.244.007 - Fax: 977.224.517 > e-mail: [EMAIL PROTECTED] > ******************************************************** > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
