Hi, we have the same problem and i got some hints from this mailing list. Even if i can't know if you have memory leaks, i can tell, that we don't have any ... we profiled a lot of time! Another fact for this is, that memory usage doesn't change.
The problem occurs at out servers only in services which uses jsp-pages...servlets work fine over serveral weeks. Another hint was to use jdk1.3 instead of 1.4, but it only changes the online-time from a day to three. Nearly same for using http-listener istead of AJP13 in connection to Apache mod_jk. What wonders me too is, that really no message is writen to any log-file. The second is, that we are unable to reproduce the problem with heavy-usage tests or so on. We're not sure what it can be, but i think it depends either on jsp-engine, or in abstract request-handler or container-communication and what we can say is, that its plattform-independent and in all 4.x -versions of tomcat. So far ... may be there are some new hints ... otherwise we have to change the container. I hope that somebody takes the problem serious! Regards, Bj�rn Clemens > -----Urspr�ngliche Nachricht----- > Von: karthikeyan vks [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 24. M�rz 2003 12:19 > An: [EMAIL PROTECTED] > Betreff: Frequent hanging > > > Dear Sir, > > We installed a web application using Tomcat 4.0. > It is a SQL 2000/ Tomcat 4.0. > > We observed a problem. > The application is getting hanging on every 4 days. > Once we restarted the Tomcat, it is ok. > > I need a clarification that why should i restart tomcat everytime? > If it has to be done, can it be automated (at present, we are > physically go > to the server room and do restart) > (Or) > Is there any installation parameters to be initialized? > > Regards, > Karthikeyan VKS > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
