Hi Yoav and Antonio, I am not absolutely sure, but I think (with high probability) that the bug is in our application. I am not original author of this application but I have to take care about it. Now I know that there are some strangenesses in source code of this app.
Yet one reason why I think that it is in our app. The server stops answer on http (but it still answers on https). It is still running. I have to stop it. During the standard stopping of server I can see message like "Waiting for 175 instance(s) to be deallocated" right after message about removing of this app. The problem began to occur when we started to use this app as the main web page. The app URL had been accessible for weeks before but only through the link from the old main web page. After that, the traffic has been multiplied (by 10 or 20). The problem occurs once a day (in average). But interesting is that it is not in time of the highest traffic. It occurs mainly in the morning or evening. I am going to try Antonio's proposal. Also I would like to try some profiling tool. But it will take a lot of time to find and repair something, I think. So, let's go back to my original question. I think that it is common situation that, due to the some mistake in source code, the execution of a request thread is very long or infinite. And the server should not to go down by this kind of mistakes. I send (in attachment) to you very simple example of it. Execution time of this example is about 100 seconds but imagine that it can be hours. I think that the server should stop this thread after some time period. Is this possible? How can I tell the server to do this? Thank you, Lipi > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 06, 2004 8:47 PM > To: Tomcat Users List > Subject: RE: How to limit time for Connector threads? > > > Hi, > > >What the original poster meant is not that there is a race condition in > >Tomcat, but in his own web application. > > I don't think so, but either one of us could be misinterpreting the > original post. > > Yoav Shapira > > > > > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
