It's strange that you have problem here. Based on my source code, the locator does not have any static initialization, does not even have a constructor. Therefore, it should just return instantly after initialize some variable. I wonder if the classloader have problem searching for this stuff. What you may want to do is first, make sure the service locator is the problem here. Next, you can step into it to find out what's it is doing in a debugger. You can then test the classloader theory by executing the webservice request twice. The 2nd time should be very fast since the class is already loaded by the class loader.
Hrishikesh Kumar wrote:
We have our local host in the /etc/hosts directory
127.0.0.1 localhost.localdomain localhost 6.6.6.5 applinux1.interact.nonreg applinux1
This is the line which is taking 5 secs:
getSubscriberDetailsLocator = new GetSubscriberDetailsServiceLocator();
V D <[EMAIL PROTECTED] edu> To [EMAIL PROTECTED] 08/04/2004 10:17 cc AM Subject Re: Performance issue with using Please respond to Axis [EMAIL PROTECTED] he.org
How about adding a local host entry into the host file?
Hrishikesh Kumar wrote:
We are using 1.2 Beta version on Linux with Tomcat. This is what is givingis
such high time. We tested the same 1.2 Beta same program on WINNT and it
working within .5 seconds. We are still working on changing the versionand
giving it a shot on Linux. I do not know about the network setting as the testing is being done by having the client and server on the same machine.
Vy Ho
<[EMAIL PROTECTED]
edu> To
[EMAIL PROTECTED]
08/03/2004 11:08 cc
PM
Subject
Re: Performance issue with using
Please respond to Axis
[EMAIL PROTECTED]
he.org
Check your network connection settings, such as hosts file, etc. Other than that, you can find a hello world tutorial for axis somewhere complete with client and server to make sure there's nothing wrong with the way you do it. 5 seconds long is just plain wrong, so definitely you're having some problem that is not soap, webservice or axis related.
Hrishikesh Kumar wrote:
Actually whatever we have written is almost as simple as a hello world problem. According to our initial analysis we are finding the getServiceLocator taking like half of the turnaround time (5 secs) in our case.