Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of roland.lammel@gmail.com
 designates 66.249.82.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=rHru+1H24g0UXoPZNlVZBCol7S82ReXzC6kkdqUDDV9GZyRK2Tg+kYwWNiHhRkfwzTvFeaKHaKiAxJAO7Paa3DrV1y95tD7ecsX2/EaM2Jo3SW1xkbpICSKssD+x2u+nI53CvFsc9ES5dQN2QQQMYsNPLnTND+NfMdh/sbHrElk=
Message-ID: <9b51ffb30701090751y4b7ce21ak2c0befd0bfe21559@mail.gmail.com>
Date: Tue, 9 Jan 2007 16:51:58 +0100
From: "Roland Lammel" <rl@brabbel.net>
Sender: roland.lammel@gmail.com
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Tomcat5.5 webserver unstable
In-Reply-To: <8232585.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_68349_12414126.1168357918586"
References: <8232585.post@talk.nabble.com>

------=_Part_68349_12414126.1168357918586
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This looks more like your application(s) is keeping the threads busy. So
tomcat is running out of free threads/workers to handle the incoming
requests.

You are either having a generic problem in your application where your
application is not closing the request hence keeping the thread occupied, or
simply been under heavy load where actually more than 200 requests had to be
handled in a very short time (this could especially happen if you serve
complex long loading pages and have high number of concurrent requests in
that period).

You could
- increase the maxthreads for the connector in server.xml
- decrease connectionTimeout / maxKeepAliveRequests of the connector in case
clients are causing the issue
- Try to find the application logic that does not end the request (or keeps
hanging in the background doing some external data queries)

Cheers

+rl

On 1/9/07, mocherla14 <ravi.mocherla@gmail.com> wrote:
>
>
> EFFECT:
> Tomcat server goes down now and then for no reason.
> The GUI can not be accesed.
> Problem has been facin even and then
>
> DESCRIPTION:
> This is the line in the Catalina log file:
>
> Dec 5, 2006 11:33:07 AM org.apache.tomcat.util.threads.ThreadPool logFull
> SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
> (200) or check the servlet status
>
>
> some soultions i had found but not sure
> The threadlock is likely in whatever webapp you're running, or less likely
> a
> thread issue between your JDK and OS (which I would guess is Linux). As a
> stopgap, you might try setting the thread timeout parameter (don't know
> the
> exact syntax offhand) to something fairly low so Tomcat will destroy any
> hanging threads after a certain period of time.
>
>
> plz kindly help with more deatiled answers.
> --
> View this message in context:
> http://www.nabble.com/Tomcat5.5-webserver-unstable-tf2944124.html#a8232585
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


-- 
Roland Lammel

"Enjoy your job, make lots of money, work within the law. Choose any two."

------=_Part_68349_12414126.1168357918586--