axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Bakker (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Created: (AXIS-1915) org.apache.axis.wsdl.gen.Parser performance on large WSDL's
Date Wed, 06 Apr 2005 11:36:25 GMT
org.apache.axis.wsdl.gen.Parser performance on large WSDL's
-----------------------------------------------------------

         Key: AXIS-1915
         URL: http://issues.apache.org/jira/browse/AXIS-1915
     Project: Axis
        Type: Bug
  Components: WSDL processing  
    Versions: 1.2RC3    
 Environment: WinXP, Java 1.4.2_06-b03, Axis 1.2RC3 (also Axis 1.1 final) (Hardware: 1.8 GHz
Intel Pentium, 384 MB of RAM)
    Reporter: Paul Bakker


Hi, 

My first post here, so please don't shoot me if I forgot to mention vital stuff, or posted
this in the wrong area.

I'm using the DynamicInvoker example and run into timeout errors. I traced it back to org.apache.axis.wsdl.gen.Parser.

Got the following code:
wsdlParser = new Parser();
wsdlParser.run(wsdlURL);

I run this, with as wsdlURL: http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

This takes about 9 seconds, with the CPU running at 100%

When I run the same, but for wsdlURL: 

"http://developer.ebay.com/webservices/latest/eBaySvc.wsdl" 
I get a timeout message:

"java.io.IOException: WSDL2Java emitter timed out (this often means the =WSDL at the specified
URL is inaccessible)!"

I have set the Timeout to 15 minutes, but still get the timeout message. All the while, the
CPU is at 100%. After the timeout, the CPU remains at 100%, untill I kill the process through
TaskManager.

Making sure it's not the Internet connection, I downloaded the WSDL to file and performed
the same action. The result is the same.

As described in the Environment section, I first ran into this issue while workign on Axis
1.1 final. I then downloaded 1.2RC3 in the hope it would been solved there, but unfortunatly,
it hasn't.

I've search the internet to see if other have had this issue. The only thing I found was setting
a longer Timeout...

Regards,

Paul Bakker





-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message