This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I think the problem is more frequently related to how long the browser will try to keep the connection open, not the limit in Tomcat. However you might check the connectionTimeout in the server.xml Connector element. <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" [ March 13, 2004: Message edited by: William Brogden ]
Joined: Nov 07, 2002
I'm facing a really bad problem! some times a thread spends too much time in a servie method (some times in a synchronized block) this blocks other threads and the hole thing goes down! any advise? The cause of threads spending lots of time in the service method is because they try to use a data base resource allready blocked by some user (outside the aplication), that forgets to release this resource!
Author and all-around good cowpoke
Joined: Mar 22, 2000
There have been a number of related discussions in the servlet forum about requests that take a long time. You could probably find them by searching. Generally, the conclusion is that you should start a separate Thread in a Runnable object that tries to perform the time-consuming operation, while the request/response Thread writes something reasonable back to the client. Naturally you keep a reference to the worker class in the session so that subsequent requests can look to see how well it is doing.