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 (athena.apache.org: domain of shakahshakah@gmail.com
 designates 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bxb2WhW2escGd4K8VlVw4jgmp1ARuCbmvP4kDh3qs/O7o8x+mKSInXRujRf8JeCxTBM6nGaJCRMsRfu0GYbo4Xi4yK+t1RdO/yuPjaACxEIsW7/reVBu7IPmaFKUoGErxTz3VSUhSz30/rtc4GbYc70H8Y6xtjHOe43lXUjQK2E=
Message-ID: <c2ee6dbd0709211055n12bfefebw2f39f7426bdef764@mail.gmail.com>
Date: Fri, 21 Sep 2007 13:55:48 -0400
From: "Jim Cox" <shakahshakah@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: 100% cpu usage by "VM Thread" in tomcat
In-Reply-To: <46F3FB48.1070101@netscape.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46F3FB48.1070101@netscape.net>

On 9/21/07, Lindsay Patten <BLindsayPatten@netscape.net> wrote:
[ ...stuff elided...]
>
> If I look at the system status using the Tomcat manager webapp there are
> often requests listed with ridiculously large values in the Time column,
> several hundred seconds for jsp pages that only take a fraction of a
> second to generate, and I can cut an paste the request into my browser
> and the request will finish in a fraction of a second.
>
[ ...stuff elided...]

As far as that goes, I've seen such threads on a Solaris box running
Tomcat 5.0.19. I can recreate them at will by requesting a JSP page in
a browser (Firefox, in this case) and making a request for another
page before I've received the response from the first request. In that
case the http80-Processor thread appears to time out after 8 minutes
of inactivity. I suppose if that happened a lot (e.g. if a network
burp caused a bunch of those) you might max out your "http processor"
threads, but that situation would be easy to spot in the thread dump.

FWIW, the "kill -QUIT <pid>" thread dump in these cases is along the lines of:
"http80-Processor22" daemon prio=5 tid=0x00430600 nid=0x227 runnable
[0xae17f000..0xae1819c8]
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:757)
        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:436)

---------------------------------------------------------------------
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