tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: Initial test of APR on Solaris
Date Tue, 03 May 2005 14:31:59 GMT

----- Original Message ----- 
From: "Remy Maucherat" <remm@apache.org>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, May 03, 2005 1:43 AM
Subject: Re: Initial test of APR on Solaris


>Bill Barker wrote:
>> Yeah, that works for me as well.  My problem now is that the APRized HTTP
>> Connector dies about 70% of the way through a test when I use the 
>> HTTPClient
>> option in JMeter.  A thread-dump shows all of the Workers waiting, and 
>> the
>> Poller polling, but nothing is happening.  It's a bit happier when I
>
>There's not much wrong with that situation, since it's a bit hard to tell 
>what the client is doing. Maybe it's the 62 sized poller causing trouble if 
>running on Windows (you should get a message about that), in which case 
>you'd need to build APR from scratch. Is the Acceptor thread still 
>accepting and giving that to the workers ?

Only JMeter is running on Windows, and yes, the Acceptor is still accepting. 
I'm guessing it's a JMeter problem, since it's just too consistant.

>
>> restrict maxThreads, but it still doesn't finish.  The Java HTTP 
>> Connector
>> finishes the test fine.
>>
>> Not using the HTTPClient option works Ok, but the actual concurrency 
>> level
>> is much lower.
>
>It's hard to tell what is going wrong. Is there logging showing attempted 
>requests and failure codes ?
>

Interestingly, the non-HTTPClient option never seems to get above ~62 
concurrency.



>Rémy
>



This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.



Mime
View raw message