tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Initial test of APR on Solaris
Date Tue, 03 May 2005 00:46:06 GMT

----- Original Message -----
From: "Remy Maucherat" <>
To: "Tomcat Developers List" <>
Sent: Monday, May 02, 2005 3:59 PM
Subject: Re: Initial test of APR on Solaris

>Bill Barker wrote:
>> I was surprised that it worked at 150.  I guess my crappy XP box was too
>> slow to give real throughput :).
>> The OOM message came from ThreadPool, which doesn't log stack traces.
>> I'll need to hack ThreadPool to see where it's getting thrown from.  The
>> box is pretty old and small (which is why it's mostly a test-bed these
>> days :), but the memory usage reported by 'top' wasn't that high.  It's
>> probably some other resource, since Sun throws OOM for everything.  I'll
>> see if I can find out Monday.
>Right, I see the error now. The issue seems to be that the APRized HTTP
>connector is apparently using a little more memory than the regular
>connector (something like 10% more). Increasing mx fixes it without
>further issues (on Windows). The regular HTTP produces the same
>stackless OOM with only a few more concurrent requests (350 starts
>causing some trouble for me) if using the standard JVM memory settings.

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


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.

View raw message