Hi,
When I see this error my first check is thread pool on server side (is it
exhausted?) next firewall. In your case (I suspect ) low ramp-up cause that
server can't serve all request at once - part of them are serviced and part
are waiting in accept() backlog queue (which is limited) but others
The most straightforward explanation is that the web server limits the
connection pool and so requests beyond that limit have to wait for a
free server-side socket. If the server is getting overloaded, some
percentage of these will not be accepted before timing out on the client
side.
If your serv
l Message-
> From: Mike Stover [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 2002 6:09 PM
> To: JMeter Users List
> Subject: RE: Connection timed out !!!
>
>
> Did you record these requests using JMeter's recording proxy? I suspect there's
> some we
Michal Kostrzewa wrote:
>>I've had trouble in the past with JMeter when not using JDK 1.4. If its
>>possible for you to run JMeter under JDK 1.4, I'd recommend trying that. My
>>problems had to do with using the proxy to record, but I think it's
>>possibel that other JDK version related problems m
>
> I've had trouble in the past with JMeter when not using JDK 1.4. If its
> possible for you to run JMeter under JDK 1.4, I'd recommend trying that. My
> problems had to do with using the proxy to record, but I think it's
> possibel that other JDK version related problems may be present.
Good p
Hi Guillaume,
I've had trouble in the past with JMeter when not using JDK 1.4. If its
possible for you to run JMeter under JDK 1.4, I'd recommend trying that. My
problems had to do with using the proxy to record, but I think it's possibel
that other JDK version related problems may be present.
Title: RE: Connection timed out !!!
Mike,
I did not use the record mode with proxy beacause I was
not able to make it working correctly.
I mofidied my thread group removing some of controllers.
The test is now simpler but seems to work better.
When I increase the # threads I get some out of
this thread even with 500 users, it is okay,
> no connection timed out to be noticed.
>
> -Guillaume
>
> -Original Message-
> From: Mike Stover [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 14, 2002 7:36 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Connection tim
-Original Message-
From: Mike Stover [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 14, 2002 7:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Connection timed out !!!
Using telnet to test an HTTP port is kind of weird. What happens when you request
13.202.220.44:2828/askonce.jsp in your browser
Using telnet to test an HTTP port is kind of weird. What happens when you request
13.202.220.44:2828/askonce.jsp in your browser?
-Mike
On 14 Oct 2002 at 19:25, Vola, Guillaume wrote:
> All,
> Let me introduce myself first,
> I work in Grenoble (france) on the askOnce product.
> I'm in char
10 matches
Mail list logo
