create the configuration context once, and then pass it to each Stub when you create the stub (if you are not doing it already), that should reduce time to create the threads? --Srinath
On Wed, Jan 5, 2011 at 10:33 AM, Amila Suriarachchi <[email protected]> wrote: > > > On Tue, Jan 4, 2011 at 7:28 PM, suril <[email protected]> wrote: >> >> I am looking for some help with a performance issue that we are running >> into >> with Axis2. >> >> We have a library that creates a pool of connections to a server. The >> connection pool is created using Apache Commons Pool. We are creating an >> Axis2 stub instance in the library and using that for the SOAP >> communication. >> >> We are running into significant performance problems with the Axis2 stub >> object invocation under load. >> >> I had 2 questions on this: >> 1) Can we re-use the same Axis2 stub instance across threads in our >> library? >> We are using Axis2 1.4 -- we can move to a higher version if needed > > you can not use stubs across threads. But you can use Axis2 1.5.4 latest > version which reuse the connections. > > thanks, > Amila. > >> >> 2) If this is not possible, then are there any suggestions/tips to >> optimize >> the performance and reduce the time taken for the Axis2 stub object >> creation? >> >> Thanks for your help >> -- >> View this message in context: >> http://old.nabble.com/Axis2-stub-creation-performance-issue-tp30586755p30586755.html >> Sent from the Axis - Dev mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > -- ============================ Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Lecturer, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
