The Http10Connector has issues with XP :(. Most of them require that you
set the 'socketCloseDelay' attribute on the connector (e.g
'socketCloseDelay="1000"' to add a one-second delay). However, this is
usually a problem with POSTed messages.
>From your description, it's sounding like you need to increase your
maxThreads setting on the Connector. I'm guessing that you are throwing
more requests at the box then it is configured to handle. You can mitigate
this somewhat by increasing the 'backlog' setting, but it mostly just shifts
the problem to your TCP stack.
You could also try using the CoyoteConnector2 from the nightly (which is
basically the same HTTP/1.1 connector that TC 4.1.x & TC 5.x are using). It
tends to work much better on XP (well, actually, it works much better in
general :).
"Dave Brewster" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
We're running a load script on our tomcat server and seeing connection
refused errors on the client.
Server Configuration:
Vanilla tomcat (not fronted with Apache) 3.3.1
-Xmx 800MB -Xms512M
Windows XP
2.8 Ghz Hyperthreaded 800Mhz front side bus, 1 CPU
1.5 GB memory.
On the client load test we are using Java, connection with the URL class.
We see (don't know if it's immediate yet) a connection refused error only
under load. The higher the number of concurrent users (or load in general),
the more errors.
Has anyone else seen this problem?
Btw... we tried fronting this with Apache, mod_jk and found we received 500
errors instead. Mod_jk got the connection refused errors instead.
Thanks,
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
