why so much connections (ports) will be created.
Maarten
-Oorspronkelijk bericht-
Van: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 29 november 2005 21:00
Aan: Tomcat Users List
Onderwerp: RE: web client running out of ports! (timeout exception)
> From: Mag
> From: Magyar, Bence [mailto:[EMAIL PROTECTED]
> Subject: RE: web client running out of ports! (timeout exception)
>
> Shouldn't I be getting persistent, reusable connections as
> the default with HTTP/1.1?
I'm sure you are - but it's the client's responsib
with
HTTP/1.1?
B.M
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote: > From: Magyar, Bence
[mailto:[EMAIL PROTECTED]
> Subject: web client running out of ports! (timeout exception)
>
> Every time I call a method, my java client opens a new port!
If
> From: Magyar, Bence [mailto:[EMAIL PROTECTED]
> Subject: web client running out of ports! (timeout exception)
>
> Every time I call a method, my java client opens a new port!
If I'm understanding the problem correctly, I don't see how changing
anything in the Tomcat
Hello, I noticed some strange behavior the other day while load testing my simple web service. First, my environment: I am running Apache Tomcat 5.5.12 with Axis 1.3 on an XP box. I've used Java2WSDL and WSDL2Java to generate the necessary bindings. I used the generated .wsdd file to deplo
