You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Hrishikesh Kumar <Hr...@caritor.com> on 2004/08/03 06:05:18 UTC
Performance issue with using Axis
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 around 10 seconds which seems to be not
acceptable to our clients at all. They are expecting a turnaround time of 1
sec. Since we are using Axis for everything: the creation of connection at
the client side, making a request, authentication, databinding on the
server side, parsing the gotten xml on the client side we are thinking that
it is causing the problem. Can you please guide me where and how we can
improve the performance.
Any tips will be appreciated and I can answer any questions if you have.
Thanks,
Hrishikesh.
Re: Performance issue with using Axis
Posted by Frank Cohen <fc...@pushtotest.com>.
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 happy to offer a few suggestions.
-Frank Cohen
PushToTest
fcohen@pushtotest.com
Phone: 408 374 7426 (USA, California, Pacific Time)
On Aug 2, 2004, at 9:05 PM, 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 around 10 seconds which seems to be not
> acceptable to our clients at all. They are expecting a turnaround time
> of 1
> sec. Since we are using Axis for everything: the creation of
> connection at
> the client side, making a request, authentication, databinding on the
> server side, parsing the gotten xml on the client side we are thinking
> that
> it is causing the problem. Can you please guide me where and how we can
> improve the performance.
>
> Any tips will be appreciated and I can answer any questions if you
> have.
>
> Thanks,
> Hrishikesh.
>
>
---
Frank Cohen, Founder, http://www.PushToTest.com, phone: 408 374 7426 USA
PushToTest offers free open-source test software and global service
solutions that test, monitor and automate Web Service systems for
functionality, scalability and performance.
Location of .properties and .xml configuration files (and .JARs)?
Posted by Martin Olsson <mn...@minimum.se>.
There is also another thing that I have been thinking about. My web
services "main class" uses several configuration files, where should I put
these? The class itself it tucked away in a .JAR inside lib/ but I feel
uncomfortable storing configuration files in the lib/ dir and while
putting them inside the JAR would work that would also make it hard to
edit them.
This issue is very similar to the problem I had yesterday, how can I store
my third-party library .JARs so that they are organized per web service?
Dumping everything in lib/ feels ugly. Surely, someone has encountered
this situation before?
---
btw, thanks Florian -- the mail.jar/activation.jar was right on.
Regards,
Martin Olsson
> You can find the first class in activation.jar and the latter in mail.jar.
> Both libs can be downloaded from java.sun.com and it's enough to put them
> in the /lib directory of your application or in the common /lib directory
> of your web server. You do not need the entire J2EE stuff...
>
> -----Ursprüngliche Nachricht-----
> Von: Martin Olsson [mailto:mnemo@minimum.se]
> Gesendet: Donnerstag, 5. August 2004 15:10
> An: axis-user@ws.apache.org
> Betreff: In which .JAR can I find DataHandler and MimeMultipart classes?
>
>
> The Axis ant-task for administration keeps asking for two classes called
> javax.activation.DataHandler and javax.mail.internet.MimeMultipart.
>
> In which .JAR file can I find these?
> Is there an open-source implementation of these?
> Must I install the entire J2EE SDK just to create a web service?
>
>
> Regards,
> Martin Olsson
>
>
>
>
AW: In which .JAR can I find DataHandler and MimeMultipart classes?
Posted by Florian Theurich <fl...@x-cellcom.de>.
You can find the first class in activation.jar and the latter in mail.jar.
Both libs can be downloaded from java.sun.com and it's enough to put them in
the /lib directory of your application or in the common /lib directory of
your web server. You do not need the entire J2EE stuff...
-----Ursprüngliche Nachricht-----
Von: Martin Olsson [mailto:mnemo@minimum.se]
Gesendet: Donnerstag, 5. August 2004 15:10
An: axis-user@ws.apache.org
Betreff: In which .JAR can I find DataHandler and MimeMultipart classes?
The Axis ant-task for administration keeps asking for two classes called
javax.activation.DataHandler and javax.mail.internet.MimeMultipart.
In which .JAR file can I find these?
Is there an open-source implementation of these?
Must I install the entire J2EE SDK just to create a web service?
Regards,
Martin Olsson
In which .JAR can I find DataHandler and MimeMultipart classes?
Posted by Martin Olsson <mn...@minimum.se>.
The Axis ant-task for administration keeps asking for two classes called
javax.activation.DataHandler and javax.mail.internet.MimeMultipart.
In which .JAR file can I find these?
Is there an open-source implementation of these?
Must I install the entire J2EE SDK just to create a web service?
Regards,
Martin Olsson
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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.GetSubscriberDetailsClient 09886454995
Vy Ho
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/06/2004 07:43 cc
PM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
he.org
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 point.
Can you try to use the webbrowser, point to the webservice's address (do
this only the first time, if want to try again, have to quit and start
the browser again, else it'll be quick), and see how long does it take.
Make sure to append ?WSDL to the end of your webservice address.
Again, you check your networking. You may have to ask a different group
here.
As a catch all thing, nothing is definite when it comes to programming.
So don't bet it all on the networking, it could be anything though.
Hrishikesh Kumar wrote:
>
>
>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.
>
>
>
>
> Vy Ho
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/05/2004 08:00 cc
> PM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
>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
>>
>>
>
>
>
>> <st946tbf@drexel.
>>
>>
>
>
>
>> edu> To
>>
>>
>
>
>
>> axis-user@ws.apache.org
>>
>>
>
>
>
>> 08/04/2004 10:17 cc
>>
>>
>
>
>
>> AM
>>
>>
>
>
>
>> Subject
>>
>>
>
>
>
>> Re: Performance issue with using
>>
>>
>
>
>
>> Please respond to Axis
>>
>>
>
>
>
>> axis-user@ws.apac
>>
>>
>
>
>
>> 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
>>>
>>>
>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 as
the
>>>testing is being done by having the client and server on the same
>>>
>>>
>machine.
>
>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Vy Ho
>>>
>>>
>>>
>>>
>>
>>
>>
>>> <st946tbf@drexel.
>>>
>>>
>>>
>>>
>>
>>
>>
>>> edu> To
>>>
>>>
>>>
>>>
>>
>>
>>
>>> axis-user@ws.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>>> 08/03/2004 11:08 cc
>>>
>>>
>>>
>>>
>>
>>
>>
>>> PM
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Subject
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Re: Performance issue with using
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Please respond to Axis
>>>
>>>
>>>
>>>
>>
>>
>>
>>> axis-user@ws.apac
>>>
>>>
>>>
>>>
>>
>>
>>
>>> 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.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by Vy Ho <st...@drexel.edu>.
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 point.
Can you try to use the webbrowser, point to the webservice's address (do
this only the first time, if want to try again, have to quit and start
the browser again, else it'll be quick), and see how long does it take.
Make sure to append ?WSDL to the end of your webservice address.
Again, you check your networking. You may have to ask a different group
here.
As a catch all thing, nothing is definite when it comes to programming.
So don't bet it all on the networking, it could be anything though.
Hrishikesh Kumar wrote:
>
>
>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.
>
>
>
>
> Vy Ho
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/05/2004 08:00 cc
> PM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
>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
>>
>>
>
>
>
>> <st946tbf@drexel.
>>
>>
>
>
>
>> edu> To
>>
>>
>
>
>
>> axis-user@ws.apache.org
>>
>>
>
>
>
>> 08/04/2004 10:17 cc
>>
>>
>
>
>
>> AM
>>
>>
>
>
>
>> Subject
>>
>>
>
>
>
>> Re: Performance issue with using
>>
>>
>
>
>
>> Please respond to Axis
>>
>>
>
>
>
>> axis-user@ws.apac
>>
>>
>
>
>
>> 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
>>>
>>>
>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 as the
>>>testing is being done by having the client and server on the same
>>>
>>>
>machine.
>
>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Vy Ho
>>>
>>>
>>>
>>>
>>
>>
>>
>>> <st946tbf@drexel.
>>>
>>>
>>>
>>>
>>
>>
>>
>>> edu> To
>>>
>>>
>>>
>>>
>>
>>
>>
>>> axis-user@ws.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>>> 08/03/2004 11:08 cc
>>>
>>>
>>>
>>>
>>
>>
>>
>>> PM
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Subject
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Re: Performance issue with using
>>>
>>>
>>>
>>>
>>
>>
>>
>>> Please respond to Axis
>>>
>>>
>>>
>>>
>>
>>
>>
>>> axis-user@ws.apac
>>>
>>>
>>>
>>>
>>
>>
>>
>>> 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.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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.
Vy Ho
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/05/2004 08:00 cc
PM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
he.org
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
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/04/2004 10:17 cc
> AM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> 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
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 as the
>>testing is being done by having the client and server on the same
machine.
>>
>>
>>
>>
>>
>>
>
>
>
>> Vy Ho
>>
>>
>
>
>
>> <st946tbf@drexel.
>>
>>
>
>
>
>> edu> To
>>
>>
>
>
>
>> axis-user@ws.apache.org
>>
>>
>
>
>
>> 08/03/2004 11:08 cc
>>
>>
>
>
>
>> PM
>>
>>
>
>
>
>> Subject
>>
>>
>
>
>
>> Re: Performance issue with using
>>
>>
>
>
>
>> Please respond to Axis
>>
>>
>
>
>
>> axis-user@ws.apac
>>
>>
>
>
>
>> 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.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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.
Vy Ho
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/05/2004 08:00 cc
PM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
he.org
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
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/04/2004 10:17 cc
> AM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> 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
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 as the
>>testing is being done by having the client and server on the same
machine.
>>
>>
>>
>>
>>
>>
>
>
>
>> Vy Ho
>>
>>
>
>
>
>> <st946tbf@drexel.
>>
>>
>
>
>
>> edu> To
>>
>>
>
>
>
>> axis-user@ws.apache.org
>>
>>
>
>
>
>> 08/03/2004 11:08 cc
>>
>>
>
>
>
>> PM
>>
>>
>
>
>
>> Subject
>>
>>
>
>
>
>> Re: Performance issue with using
>>
>>
>
>
>
>> Please respond to Axis
>>
>>
>
>
>
>> axis-user@ws.apac
>>
>>
>
>
>
>> 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.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by Vy Ho <st...@drexel.edu>.
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
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/04/2004 10:17 cc
> AM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> 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 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 as the
>>testing is being done by having the client and server on the same machine.
>>
>>
>>
>>
>>
>>
>
>
>
>> Vy Ho
>>
>>
>
>
>
>> <st946tbf@drexel.
>>
>>
>
>
>
>> edu> To
>>
>>
>
>
>
>> axis-user@ws.apache.org
>>
>>
>
>
>
>> 08/03/2004 11:08 cc
>>
>>
>
>
>
>> PM
>>
>>
>
>
>
>> Subject
>>
>>
>
>
>
>> Re: Performance issue with using
>>
>>
>
>
>
>> Please respond to Axis
>>
>>
>
>
>
>> axis-user@ws.apac
>>
>>
>
>
>
>> 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.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Re: ServiceLocator on Linux
Posted by Paul Callahan <ca...@gmail.com>.
it might be useful to build axis from source--insert some timings
around the instance method on the service locator class that is
generated by wsdl2java. particularly, the "meat" of the work looks
like it is done in the soapbindingstub, so perhaps try to put some
timings/log statements in there?
On Thu, 5 Aug 2004 11:36:59 +0530, Hrishikesh Kumar
<hr...@caritor.com> wrote:
>
>
> Hi All,
>
> Just wanted to know if anybody is executing SOAP Client using Axis on
> Linux.
>
> We are having issues getting the serviceLocator on the client side. It is
> taking 5 secs to create a servicelocator itself.
>
> Thanks,
> Hrishikesh.
>
>
ServiceLocator on Linux
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
Hi All,
Just wanted to know if anybody is executing SOAP Client using Axis on
Linux.
We are having issues getting the serviceLocator on the client side. It is
taking 5 secs to create a servicelocator itself.
Thanks,
Hrishikesh.
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/04/2004 10:17 cc
AM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
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 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 as the
>testing is being done by having the client and server on the same machine.
>
>
>
>
> Vy Ho
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/03/2004 11:08 cc
> PM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> 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.
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by V D <st...@drexel.edu>.
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 version and
>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
> <st946tbf@drexel.
> edu> To
> axis-user@ws.apache.org
> 08/03/2004 11:08 cc
> PM
> Subject
> Re: Performance issue with using
> Please respond to Axis
> axis-user@ws.apac
> 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.
>>
>>
>>
>>
>
>
>
>
>
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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 as the
testing is being done by having the client and server on the same machine.
Vy Ho
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/03/2004 11:08 cc
PM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
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.
>
>
Re: Performance issue with using Axis
Posted by Vy Ho <st...@drexel.edu>.
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.
>
>
Re: Performance issue with using Axis
Posted by Hrishikesh Kumar <Hr...@caritor.com>.
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.
V D
<st946tbf@drexel.
edu> To
axis-user@ws.apache.org
08/03/2004 10:22 cc
AM
Subject
Re: Performance issue with using
Please respond to Axis
axis-user@ws.apac
he.org
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 around 10 seconds which seems to be not
>acceptable to our clients at all. They are expecting a turnaround time of
1
>sec. Since we are using Axis for everything: the creation of connection at
>the client side, making a request, authentication, databinding on the
>server side, parsing the gotten xml on the client side we are thinking
that
>it is causing the problem. Can you please guide me where and how we can
>improve the performance.
>
> Any tips will be appreciated and I can answer any questions if you have.
>
>Thanks,
>Hrishikesh.
>
>
>
Re: Performance issue with using Axis
Posted by V D <st...@drexel.edu>.
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 around 10 seconds which seems to be not
>acceptable to our clients at all. They are expecting a turnaround time of 1
>sec. Since we are using Axis for everything: the creation of connection at
>the client side, making a request, authentication, databinding on the
>server side, parsing the gotten xml on the client side we are thinking that
>it is causing the problem. Can you please guide me where and how we can
>improve the performance.
>
> Any tips will be appreciated and I can answer any questions if you have.
>
>Thanks,
>Hrishikesh.
>
>
>