Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / October 2005

Tip: Looking for answers? Try searching our database.

Slow Axis client written in Java

Thread view: 
gord.harding@hummingbird.com - 28 Oct 2005 15:02 GMT
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
Chris Smith - 29 Oct 2005 04:43 GMT
> 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.

Signature

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

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Marc E - 30 Oct 2005 01:33 GMT
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.

>> 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
[quoted text clipped - 12 lines]
> Perhaps you'll get an error message.  Also, try running Ethereal while
> the request is made.
gord.harding@hummingbird.com - 31 Oct 2005 14:54 GMT
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.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.