Return-Path: 
 <users-return-208080-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 74551 invoked from network); 8 Feb 2010 18:09:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 8 Feb 2010 18:09:32 -0000
Received: (qmail 8223 invoked by uid 500); 8 Feb 2010 18:09:28 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 8143 invoked by uid 500); 8 Feb 2010 18:09:28 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 8132 invoked by uid 99); 8 Feb 2010 18:09:28 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2010 18:09:28 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2010 18:09:18 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1NeY2b-00039G-2H
	for users@tomcat.apache.org; Mon, 08 Feb 2010 10:08:57 -0800
Message-ID: <27503897.post@talk.nabble.com>
Date: Mon, 8 Feb 2010 10:08:57 -0800 (PST)
From: youngm <youngm@gmail.com>
To: users@tomcat.apache.org
Subject: Re: Slow requests when using "Executor" pool
In-Reply-To: <4B6B12AD.3040700@hanik.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: youngm@gmail.com
References: <27443550.post@talk.nabble.com> <4B6B12AD.3040700@hanik.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Setting maxKeepAliveRequests="1" seems to fix the issue as well.  Perhaps the
problem has something to do with keep alive requests?  Any other thoughts?

Mike


Filip Hanik - Dev Lists wrote:
> 
> turn off keep alive for your profiler to not give you false positives
> 
>   maxKeepAliveRequests="1"
> 
> 
> <Connector port="8080" protocol="HTTP/1.1" maxKeepAliveRequests="1"
>                  connectionTimeout="20000"
>                  redirectPort="8443" />
> 
> 
> 
> On 02/03/2010 02:14 PM, youngm wrote:
>> (This is a new thread spawned from my "Tomcat 6.0.24 Google Chrome"
>> thread
>> with better information)
>>
>> I'm running Tomcat 6.0.24, Sun JDKx86 6u18, Windows 7 64, Firefox and
>> Chrome
>> browser.
>>
>> I've noticed that for about the first 1-3 min after my tomcat instance
>> has
>> started some of my requests that normally take>  1 sec to be handled are
>> taking 30+ sec to respond.
>>
>> I've narrowed the problem down to my use of an Executor pool to handle
>> requests.  The follwing is my server.xml:
>>
>> <?xml version='1.0' encoding='utf-8'?>
>> <Server port="8005" shutdown="SHUTDOWN">
>>    <Listener className="org.apache.catalina.core.JasperListener" />
>>    <Listener
>> className="org.apache.catalina.mbeans.ServerLifecycleListener"
>> />
>>    <Listener
>> className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
>> />
>>    <Service name="Catalina">
>>      <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>>          maxThreads="150" minSpareThreads="4"/>
>>       <Connector executor="tomcatThreadPool"
>>                 port="8080" protocol="HTTP/1.1"
>>                 connectionTimeout="20000"
>>                 redirectPort="8443" />
>>      <Engine name="Catalina" defaultHost="localhost">
>>        <Host name="localhost"  appBase="webapps">
>>        </Host>
>>      </Engine>
>>    </Service>
>> </Server>
>>
>> If I change<Connector/>  to not use and executor like so:
>>
>> <Connector port="8080" protocol="HTTP/1.1"
>>                  connectionTimeout="20000"
>>                  redirectPort="8443" />
>>
>> I don't experience a problem.
>>
>> I've hooked a profiler up and it appears all of the time is being spent
>> doing a socketRead with the following trace:
>>
>> [Wall Time]  java.net.SocketInputStream.socketRead0(FileDescriptor,
>> byte[],
>> int, int, int)
>> java.net.SocketInputStream.read(byte[], int, int)
>> org.apache.coyote.http11.InternalInputBuffer.fill()
>> org.apache.coyote.http11.InternalInputBuffer.parseRequestLine()
>> org.apache.coyote.http11.Http11Processor.process(Socket)
>>
>> I've tried to analyse the network info with wireshark and see no
>> decernable
>> differences in network traffic between the 2 requests.  I can try
>> analyzing
>> wireshark data further if the list thinks that would be useful.  Though I
>> find it strange that it works fine when not using an Executor.
>>
>> Anyone have any ideas or seen similar behaviour?
>>
>> Thanks,
>> Mike
>>    
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Slow-requests-when-using-%22Executor%22-pool-tp27443550p27503897.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org