Thank you for your suggestion. The client and server
are not on the same machine. I can't modify the server
side, just query it with soap or axis. I tried 3 ways
to connect :
- IP address in URL constructor : 15230 ms
- logical name, using /etc/hosts : 15180 ms
- bad logical name : 13256 ms to get
How about try to add the server's ip/address to the client machine's
host file. Event if it's the same machine, add localhost in anyway.
Please let me know if that solves the initial delay.
Bernard LUPIN wrote:
Hi all,
I'm writing a client that will query web services
already developped with Apa
Thank you Tony for your explanation, but my problem is
only on the client side, since the measurements are
good when I'm using an Apache Soap 2.3.1 client.
The total time for my calls are :
ClientServerFirst callSubsequent calls
Soap Soap 3653 ms 958 ms
Axis
Bernard,
Axis is like any other web application. Depending on how
it is deployed, the first service call may have to wait for the application
server to create an instance of the Axis servlet and initialize it. In
addition, I guess Axis is doing something similar for each service that
is depl
Hi all,
Without response, I've tried to write a third client,
using WSDL2Java. My new client now looks like this :
RbServiceLocator service = new RbServiceLocator();
Rb rbStub = service.getrpcrouter();
((RbStub) rbStub).setUsername("web_user");
((RbStub) rbStub).setPassword("web_password");
resp
Hi all,
I'm writing a client that will query web services
already developped with Apache Soap 2.3.1.
I tested two versions of my client, one with Apache
Soap 2.3.1 and one with Axis 1.2RC1.
The return values are good with both clients, but the
execution time is 3 seconds with Soap 2.3.1, and 15
s
