believe the problem is in HotSpot design, and may not be machine
dependent.
Bottom line: try Java 1.2.2.5
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/8/01, 11:
try to keep people posted on my progess. Good luck,
peter
-Original Message-
From: Mark Richards [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 5:47 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Connection refused under hight load
AFAIK, this limit doesn't a
> -Original Message-
> From: Chris Janicki [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 3:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Connection refused under hight load
>
>
> Are you using Java 1.3 by any chance?
>
Yes, I
Are you using Java 1.3 by any chance?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/8/01, 8:46:56 AM, Mark Richards <[EMAIL PROTECTED]> wrote
regarding RE: Connectio
AFAIK, this limit doesn't apply for TCP/IP connections, only netbios
connections.
Mark
-Original Message-
From: Cox, Charlie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 8:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Connection refused under hight load
Title: RE: Connection refused under hight load
I know that NT4 Workstation only allows 10 concurrent network connections. I didn't think that limit had changed for Win2k Workstation. Even though your app is running on the same machine, it is still making tcpip requests which would
I'd say that you've started too many threads; when there are no more threads
available in the thread pool, Tomcat refuses connections.
You should increase the number of threads in the pool. Sadly, I don't know
how to do that; and would like to know :)
Cheers,
Alex.
Markus Ebersberger wrote:
>
Hi,
I'm testing a servlet-application that is using Tomcat v 3.1
(standalone,
without Apache) running on Win2K Workstation.
The tool I'm using for testing starts a (configurable) number of
threads,
each of which connects to the server, sends a HTTP-request and waits for
the response. It runs on t
