What the original poster meant is not that there is a race condition in Tomcat, but in his own web application.
Maybe we should try to point him into the direction of fixing the problem.
So there I go:
- When it "hangs", if on Unix/Linux, kill -QUIT your Tomcat process, and you will get some stack traces.
- Maybe they will tell you something. If they do, you're lucky. Otherwise, post them: maybe they will tell us something.
At least, you will see how many threads there are, and their state (e.g. waiting for a lock).
Good luck!
Antonio Fiol
Shapira, Yoav wrote:
Hi, I highly doubt you've stumbled on a race condition in the tomcat connector implementation. Nonetheless, if you can supply a small WAR that leads to the problem you've described, we'll be glad to test it, and if your problem is reproducible rest assured it will be fixed immediately, as that would be more important than the other stuff currently open in bugzilla.
Yoav Shapira Millennium Research Informatics
-----Original Message----- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 3:26 AM To: 'Tomcat Users List' Subject: RE: How to limit time for Connector threads?
Yes, I did it.
But it is not solution. Server doesn't answer slowly or for only some requests. It doesn't answer at all. It means that treads are not terminated and resources are not released. Sometimes, server doesn't answer without "All threads are currently busy" exception. That is why I think that the problem is some death lock.
Lipi
disableUploadTimeout="true" />-----Original Message----- From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:56 AM To: Tomcat Users List Subject: RE: How to limit time for Connector threads?
Maybe you should increase the number of threads in your connector.
check attribut maxProcessors in your server.xml In this example, I set it to 500 instead of 75 (default value)
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="80" minProcessors="30" maxProcessors="500"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
release-----Message d'origine----- De : rlipi [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 mai 2004 08:40 À : 'Tomcat Users List' Objet : How to limit time for Connector threads?
Hallo, is it possible in any way to limit time for threads that realize user requests?
Sometimes (once a day in average), the Tomcat 5.0.19 server doesn't
answers. The reason is in error message "All threads are currently
busy". Probably there is a bug in the web application. Some kind of
synchronization death lock, I think.
But localization of this bug is very hard. So, termination (and
of all resources) of long time threads can be a work around.
Thank you for any suggestions, Lipi.
--------------------------------------------------------------------- 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]
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]
smime.p7s
Description: S/MIME Cryptographic Signature
