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.
That said, I seem to "lose" threads with tomcat 3.2.1 on Linux 2.2.14 using
Sun's 1.3 JDK. What I mean is that "dead" threads pile up WELL in excess of
the thread pool limit. These threads don't seem to handle requests any
more. Tomcat slows down quite noticeably too. I'm not sure I have ever
left it up long enough to know if it might just die after enough threads
"pile" up(well, it definitely would when it hit the OS' thread limit). Are
you seeing far more threads than you would expect (well in excess of the
pool size)? Maybe we are suffering from the same malady.
-----Original Message-----
From: Thom Park [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 4:11 PM
To: [EMAIL PROTECTED]
Subject: Re: 3.2.1 Dies
You may have used up all of your free threads.
Try increasing the thread pool for the Http connector - see if it improves
the
longevity of your
tomcat instance.
-Thom
Hunter Hillegas wrote:
> Well, I am using the scripts and my Tomcat just dies after a few days of
> heavy load...
>
> We're talking hundreds of thousands of hits...
>
> Any other ideas are appreciated. I'm tempted to try 3.2.2 but since this
is
> a production site, I'm a bit scared off by the beta status of the
software.
>
> Hunter
>
> > From: "Tim O'Neil" <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > Date: Mon, 21 May 2001 12:18:52 -0700
> > To: [EMAIL PROTECTED]
> > Subject: Re: 3.2.1 Dies
> >
> >> What does running with nohup do for you?
> >>
> >> I usually start Tomcat using tomcat.sh start and then just log out...
> >
> > Me too. Nohup (no hangup) runs the command in an "ingnore
> > hangup" signal mode- not the same as a process fork. I think
> > the cmd runs as an orphaned process. If he runs it as "nohup
> > cmd &" that's pretty much what the tomcat startup script
> > does, minus the process env setup. Really he should use the
> > scripts. I'm guessing he's not using the "&" at the end of
> > the invocation, the os sees the process is orphaned after
> > a while, and kills it.
--
http://www.borland.com/newsgroups
http://www.borland.com/devsupport/disclaim.html
