I have run into a similar situation when slamming my setup with thousands of requests 
via vspider (a verity search engine that is parsing a doc tree and making HTTP 
requests for every link it parses).  What I will see (and this is on a Solaris box) is 
that the system goes into a 100% iowait state indicating some sort of deadlock 
situation.  I am still running some tests today, but what I saw as of yesterday was 
that the deadlock may indeed be caused by version 1.3.0 of Java.  I ran with 1.2.2-07 
yesterday and managed to get through a whole document tree for the first time.  I will 
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 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


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 count against the limit. This is to force people to buy NT Server.
Charlie 
-----Original Message----- 
From: Markus Ebersberger [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 08, 2001 6:13 AM 
To: [EMAIL PROTECTED] 
Subject: Connection refused under hight load 


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 the same machine as the server. 
When I start many threads simultaneously, the server sometimes refuses 
connections (I get a ConnectException on client side). 
The tomcat logfile shows nothing unusual. 
Does someone know a possible reason for this behaviour or even a 
solution ? 
(I suspect that the "connection request queue" (I don't know the correct 
 term ) of the operating system is too short, but where can i adjust 
this ?) 


Thanks in advance, 
Markus 
--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, email: [EMAIL PROTECTED] 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to