.
-Thom
Hunter Hillegas wrote:
How can I check to see if I have a lot of dead threads?
Hunter
From: Devon Ziegler [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Mon, 21 May 2001 16:43:04 -0400
To: [EMAIL PROTECTED]
Subject: RE: 3.2.1 Dies
Interesting.used up all free
I ran into a similar problem. The servlet sessions will timeout so the user
has to log in again, but that doesn't help with what you are talking about
(which seems to be cleaning up things after a user has been inactive long
enough).
I basically created a context wide vector of user sessions
Frankly it doesn't seem like it would take much work to have BOTH (newsgroup
and mailing list). Route messages arriving to one type into the other and
vice versa with some back-end software. Most of us are developers here
aren't we :)
Just a thought.
-Devon
-Original Message-
From:
Interesting.used up all free threads.increase thread pool.
shouldn't users just have to wait for a free thread if they hit the pool
limit? Increasing it should let more requests be handled simultaneously,
but how would it help longevity? I'm not saying it won't. Just skeptical.
If you include the right driver/libraries in your applet's jar you likely
COULD connect to the database from an Applet (if the database permissions
were set up so the user could connect from anywhere). I agree that this is
probably not a good idea though. The pipe that the connection uses isn't
There is a setting is server.xml relating to supporting sessions without
cookies (session id should end up in URL instead). I don't recall the exact
setting. You might need to change this setting (or I could be wrong :) ).
-Original Message-
From: Filippo Munafò [mailto:[EMAIL
Sounds like you have server.xml set up to watch for http connections on port
8080. Look for port Parameters in there and set them to 80 IF you have
root/admin rights on the machine, otherwise you will have to run it on a
higher port like 8080.
-Original Message-
From: Ajay Ejantkar
We're using Tomcat 3.21 with servlets.
I'm wondering if there is a way to notice when a browser disconnects from
the current request so that my application can stop attempting to formulate
it's response. We currently have some reports that take quite a bit of
time/resources to complete. If
We've got some strange issues with Tomcat locking during multiple
requests/high load. We are using Tomcat as the sole web server (not
behind Apache) to run a Servlet based web app. I've got the thread pool
turned on with 10 threads. There is only ONE database method that is
synchronized and a
