[mashup-dev] [Fwd: [wsas-java-dev] service archives having libs in the aar takes too long to respond]

[saminda abeyruwan]

Hi,

We also found this problem in  wsdlconverter.aar, where it contains all 
Saxon jars for XSLT 2.0 processing. As a test I changed the above aar to 
a directory "wsdlconverter" and tried the service again and it worked. 
It seems to me that the deployment is behaving differently for .aar and 
directory case. This has to be fixed in Axis2 service deployment.

Thank you

Saminda


Keith Chapman wrote:
> I switched the dependancy to WSAS-SNAPSHOT (Commented out the
> scraperTest for now, will put it back in once this gets fixed.)
> 
> Thanks,
> keith.
> 
> 
> Keith Chapman wrote:
>> FYI.
>>
>> I have not switched the dependency as yet. Wondering whether we will
>> have to wait till this gets fixed in Axis2.
>>
>> Thanks,
>> Keith.
>>
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> [wsas-java-dev] service archives having libs in the aar takes too long
>> to respond
>> From:
>> Keith Chapman <keith at wso2.com>
>> Date:
>> Thu, 06 Dec 2007 08:36:32 +0530
>> To:
>> wsas-java-dev at wso2.org
>>
>> To:
> 
> 
>> wsas-java-dev at wso2.org
>>
>>
>> Hi,
>>
>> Yesterday I was trying to switch our dependency (of the Mashup Server)
>> to WSAS-SNAPSHOT but had to put it on hold as one of our tests were
>> failing. The scraper test (the one that was failing) tries to invoke the
>> scraperservice to perform some scraping task. The reason for failure was
>> read timed out. Debugging through I noticed that the service takes a
>> hell of a lot of time to respond (with WSAS 2.1 based on Axis2-1.3 the
>> response comes in less that a second but here it was taking more than 5
>> mins and still didnt respond). Notably the scraperservice has a bunch of
>> libs in its service archive and due to its similarity with WSDLConverter
>> service in WSAS I tried converting a WSDL 1.1 to 2.0 on both WSAS 2.1
>> and SNAPSHOT.
>>
>> Guess what, 2.1 responds in less that a second and SNAPSHOT just waits
>> without responding. This seems to be some issue in Axis2.
>>
>> Note that both these services have a bunch of jars inside the aar.
>>
>> Thanks,
>> Keith
>>
>> _______________________________________________
>> Wsas-java-dev mailing list
>> Wsas-java-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Mashup-dev mailing list
>> Mashup-dev at wso2.org
>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
> 
> 
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>