Nope -
haven't seen that, can you send a snippet of code up through that point?
Are
you pulling in remote WSDL during that time - if so, that could be part of
it.
Also,
what are you setting the JVM min and max heap to?
Bumping that up may help improve performance by
reducing garbage collection time...
-----Original Message-----
From: Anecito, Anthony (HQP) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 1:05 PM
To: [EMAIL PROTECTED]
Subject: axis client code performance issueHi All,
Has anyone noticed that a client using the Axis code for setting up to" ivoke" a call to an Axis server (not actually connecting just initializing) is very slow. I am experiencing 20 - 23 seconds to just get to setting up the call object (last statement is setOperationName) on 1GHz CPU based PC. I am running Axis 1.0.
Any ideas? Is this an possibly an issue addressed in Axis 1.1? Does someone have an example that runs in under 2 seconds on a 1GHz system?
Many Thanks,
Tony
