RE: Concurrent Accesses
I'm just accessing a static html file.
Han
-Original Message-
From: peter lin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 4:15 PM
To: Tomcat Users List
Subject: Re: Concurrent Accesses
I've managed to get Tomcat to handle 100+ concurrent requests getting
dynamic pages that look at request parameters to determine which
header/footer to display. Are your tests getting static HTML files? or
are they getting dynamic pages which query a database?
peter lin
Han Wang wrote:
>
> Tomcat Users,
>
> The question is this:
> How many concurrent accesses can tomcat 4.0.3 support?
>
> Now, I know this may be a function of processing power, but my own tests
are
> showing it much lower than expected.
>
> Basically did the following:
> Created a simple java app that spawns off n threads, each thread making an
> access to a file hosted by tomcat. Code snipped shown below:
>
> At n > 17, I start getting
>
> java.net.ConnectException: Connection refused: connect
>
> The number of connetions refused is roughly proportional to the number of
> thread over 17.
>
> Is there some configuration I have to change?
> I already modified server.xml,
>
> connector acceptCount="100", minProcessors="50", maxProcessors="100" from
> the default values, with NO effect.
>
> I also tried using Apache HTTPD and ajp13 (using the same connector
settings
> as above), with no effect.
>
> I can't believe this low number is truely the # concurrent accesses that
> Tomcat can handle, this must be an artifical limit somewhere.
>
> Please advise (and thanks in advance)
> Han Wang
> [EMAIL PROTECTED]
>
> SAMPLE CODE:
>
> public class TestClient extends Thread {
> public void run() {
> URL url = new URL("http://localhost:8080/axis/";);
> InputStream in = url.openStream();
> URLConnection conn = url.openConnection();
> int len = conn.getContentLength();
> }
>
> public static void main(String[] args) {
> int n = Integer.parseInt(args[0]);
> TestClient [] threads = new TestClient[n];
>
> for (int i = 0; i threads[i] = new TestClient();
> }
>
> for (int i = 0; i threads[i].start();
> }
>
> for ( int i=0; i threads[i].join();
>
> }
> }
> }
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Concurrent Accesses
Tomcat Users,
The question is this:
How many concurrent accesses can tomcat 4.0.3 support?
Now, I know this may be a function of processing power, but my own tests are
showing it much lower than expected.
Basically did the following:
Created a simple java app that spawns off n threads, each thread making an
access to a file hosted by tomcat. Code snipped shown below:
At n > 17, I start getting
java.net.ConnectException: Connection refused: connect
The number of connetions refused is roughly proportional to the number of
thread over 17.
Is there some configuration I have to change?
I already modified server.xml,
connector acceptCount="100", minProcessors="50", maxProcessors="100" from
the default values, with NO effect.
I also tried using Apache HTTPD and ajp13 (using the same connector settings
as above), with no effect.
I can't believe this low number is truely the # concurrent accesses that
Tomcat can handle, this must be an artifical limit somewhere.
Please advise (and thanks in advance)
Han Wang
[EMAIL PROTECTED]
SAMPLE CODE:
public class TestClient extends Thread {
public void run() {
URL url = new URL("http://localhost:8080/axis/";);
InputStream in = url.openStream();
URLConnection conn = url.openConnection();
int len = conn.getContentLength();
}
public static void main(String[] args) {
int n = Integer.parseInt(args[0]);
TestClient [] threads = new TestClient[n];
for (int i = 0; imailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
RE: Threads please help
I tried the same test connecting to a solaris box, and have no problems (I stopped after trying 200 simultaneous connections) Is this a known problem with the NT version? Anyone? Han -Original Message- From: Han Wang [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 23, 2001 10:53 AM To: [EMAIL PROTECTED] Subject: Threads please help I'm having problems doing 16 or more simultaneous access of Tomcat 3.2.1 on NT I tried to hit http://localhost:8080/ with 16 or more threads. And I get connection refused for the requests after 15. Is there a limit to the number of concurrent connections? If so, how can I change it? (or is that not recommended?) Is this a NT thing? Does anyone else see this? I tried Apache and it has no problems with >100 simultaneous threads. Preemptive thanks, Han
Threads please help
I'm having problems doing 16 or more simultaneous access of Tomcat 3.2.1 on NT I tried to hit http://localhost:8080/ with 16 or more threads. And I get connection refused for the requests after 15. Is there a limit to the number of concurrent connections? If so, how can I change it? (or is that not recommended?) Is this a NT thing? Does anyone else see this? I tried Apache and it has no problems with >100 simultaneous threads. Preemptive thanks, Han
Threads
I'm doing performance testing of an application for Tomcat 3.2.1. Basically a client application accesses a service running in Tomcat/Jboss using SOAP. I have a test client that generates X number of threads to access the URL/Tomcat port(8080). The problem is that when X is greater than 15, I get connection refused. After more testing, I found that there seems to be a maximum of 15 connections per second limit. I don't think this is true, but the behavior seems to support this theory. I used the same test client to access the apache port and it supports hundreds of simultaneous connections. Is there some configuration I need to change? Is this a know limit? Any help would be appreciated. Han
