Charitha Kankanamge wrote: > We have also noticed that the WSAS server startup time significantly > increased in snapshots. Mashup server Startup times on linux
Mashup startup time with WSAS 2.1. = 29244 ms Mashup startup time with WSAS SNAPSHOT. = 58809 ms Thanks, Keith. (In my winxp box, Startup time of a fresh > WSAS2.1 instance was ~20 sec, however the latest WSAS-snapshot took ~40 > sec) > > regards > Charitha > > Keith Chapman wrote: > >> 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 >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev >> >> >> >> > > _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
