axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1199) Axis Performance problem with Wsdd configuration
Date Thu, 30 Sep 2004 09:05:32 GMT
The following comment has been added to this issue:

     Author: Venkat Reddy
    Created: Thu, 30 Sep 2004 2:04 AM
we can comment out the initTMR(), because anyway validateDescriptors calls initTMR(); but
am not sure if we can remove the call to validateDescriptors(); as well. Because validateDescriptors()
sets following three things on the JavaServiceDescription object -
 - desc.setTypeMappingRegistry(tmr)
 - desc.setTypeMapping(...)
 - desc.setAllowedMethods(methodList)

I guess these calls are required during construction becuase the method validateDescriptors
is not called from anywhere else. And if these are required, we also need the call to initTMR().

Anyone have some thoughts on this?

View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1199
    Summary: Axis Performance problem with Wsdd configuration
       Type: Bug

     Status: Open

    Project: Axis
             Deployment / Registries
             1.2 Alpha

   Assignee: Davanum Srinivas
   Reporter: Miguel Antunes

    Created: Mon, 19 Jan 2004 4:07 PM
    Updated: Thu, 30 Sep 2004 2:04 AM
Environment: Operating System: All
Platform: All

I have experienced a poor performance on Axis when using wsdd configuration 
with a large amount of services. I have deployed about 800 services in axis, 
each service with 3 methods, and two type mappings. The first time I invoke a 
service or ask for its Wsdl the response time is about one minute (the service 
execution time is about 300 ms). I have profiled Axis and found that most of 
the time was spent in the org.apache.axis.deployment.wsdd.WSDDService 
constructor, more precisely in its last two statements:
" ...
        // Initialize TypeMappingRegistry

        // call to validate standard descriptors for this service

After looking at the class more carefully I noticed that axis is prepared for 
on demand initialization so I just commented out those two lines, the results 
were very satisfactory. The following table gives a little resume:
                      Before optimization          After optimization

List all service          +- 120 sec                    60 sec

First service wsdl         >60 sec                        <10 sec
query after boot

First service call         >60 sec                        <10 sec
after boot
Note: Since these numbers were obtained in my development environment, their 
absolute values are not relevant. What is relevant is the difference between 
the numbers for the two axis versions.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message