If you deploy your servlet with an application deployment scope, you will have
just one instance of the server classes instantiated. Multiple clients can
still call into your web service, but you have to make sure that your member
data is thread-safe.
James Black [EMAIL PROTECTED] wrote:
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 deploy
?
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 I'm understanding the problem correctly, I don't see
point me in the right direction, it would be much appreciated. Thanks!
B.M
Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Magyar, Bence
[mailto:[EMAIL PROTECTED]
Subject: RE: web client running out of ports! (timeout exception)
Shouldn't I be getting persistent, reusable
