The performance improved when we copied all the jars the client depends on
to one folder and executed the client in the following way. This again is
not consistent across two linux machines. But if anybody has the idea,
please do let me know.
java -Djava.endorsed.dirs=.
com.interact.api.client
lto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Performance issue with using Axis
It's class loader if the creation of a new locator took that long. I
strongly think that is not the case. Chance is very high that your
networking configuration is
It's class loader if the creation of a new locator took that long. I
strongly think that is not the case. Chance is very high that your
networking configuration is bad. Check the host file again, and you can
also ask people who are expert in this area. I am sure it's your
networking at this
Hi,
Yes, the first time execution of this call will take like 6 seconds, but
the subsequest calls to this method takes just 100 milli seconds. Do you
think there is problem with classloader, if that is case please suggest me
somethings to try.
Thanks,
Hrishikesh.
Thanks for the replies. Actually it is very strange. This is happening only
at our client's site. I have a windows machine where I run the same client
and the execution is happening just like you have mentioned.
I will try your suggestions and let you know.
Regards,
Hrishikesh.
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 stuf
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();
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 giving
such high time. We tested the same 1.2 Beta same program on WINNT and it is
working within .5 seconds. We are still working on changing the ver
We are using 1.2 Beta version on Linux with Tomcat. This is what is giving
such high time. We tested the same 1.2 Beta same program on WINNT and it is
working within .5 seconds. We are still working on changing the version and
giving it a shot on Linux. I do not know about the network setting a
Hi Hrishikesh: I would be happy to offer advice on how to improve the
system's performance. I recommend you take a look at the
http://www.pushtotest.com site for a list of resources and articles on
improving SOA scalability and performance. Additionally, if you would
send me the WSDL I would be
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
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.
Thanks,
Hrishikesh.
Maybe try a hello world problem first. It should take you couple mili
seconds.
Hrishikesh Kumar wrote:
Hi All,
We have implemented a Web Service using Axis. We have also developed Java
clients using the stubs created by Axis (WSDL). A simple call which returns
like some 10 tags is taking aroun
13 matches
Mail list logo
