Slow Axis client written in Java

G

gord.harding

During some testing of my Web Service, written in Java using Axis, I
ran into some extremely slow times.

Simple Web Service calls would take in excess of 2000 ms. I am
conversing with a web service on my own machine. (Remote machines times
are similar but about 150 ms longer.)

In order to determine if my client was the issue I wrote a similar
client in J#. The exact same calls returned in 16-100 ms.

I can only assume that I am missing something with my setup of the Java
client but have been unable to unearth answers.

Has anybody seen similar problems or does anybody have a suggestion on
how to tune this.

I am using Axis 1.2.1 for Java.

BTW, I put some timing in the client and service. It would appear that
the web service is getting the request about 2000 ms after the client
has sent it. On the return message the delay is about 10-20 ms. So all
the problem appears to be in getting the message to the client.

Thanks for any help
Gord
 
C

Chris Smith

Simple Web Service calls would take in excess of 2000 ms. I am
conversing with a web service on my own machine. (Remote machines times
are similar but about 150 ms longer.)

In order to determine if my client was the issue I wrote a similar
client in J#. The exact same calls returned in 16-100 ms.

Based on this information, my guesses might include DNS lookup or other
network access in building the request. Network access might be due to
some kind of logging, or to finding an XML Schema or DTD to validate
against while building the XML document.

To prod further in this direction, you might try running the code from a
system with no internet connection or DNS access, and see what happens.
Perhaps you'll get an error message. Also, try running Ethereal while
the request is made.

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
 
M

Marc E

i've been having the same problem. But for me, 2000 ms is nothing...i'll see
10+ seconds before the client request hits the wire.

If you get anywhere with this, please post back.
 
G

gord.harding

Although I thought I got around this by trying the IP address,
localhost and 127.0.0.1.

In addition I will try putting the host name in the hosts file.

I will give this a try.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,776
Messages
2,569,603
Members
45,189
Latest member
CryptoTaxSoftware

Latest Threads

Top