I haven't followed this thread fully, but if this is a plain Java project then I
recommend using TPTP (www.eclipse.org) for profiling.
Regards,
Jimisola
----- Original Message -----
From: "Josef Bajada" <[EMAIL PROTECTED]>
To: <xmlrpc-dev@ws.apache.org>
Sent: Saturday, February 18, 2006 4:09 AM
Subject: Re: XmlRpc.execute() sometimes takes long
Hi Jochen,
I am just asking if any of the developers know anything about this! I will
put some logging into the source and see which activity is taking so long.
Unfortunately at the moment these are the only facts I have. I'll let you
know if I find anything new.
Josef
On 2/17/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
Josef Bajada wrote:
> I am suspecting that the XmlRpcServer.execute() method is sometimes, for
> some reason, taking too long to execute my method.
>
> Any idea what part of the XmlRpcServer.execute() could take long? From a
> quick look I gave it there doesnt seem to be anything that should take
too
> much time. Maybe the way the worker pool stack is working?
You give us no hard facts, just questions. Knowing our code, I see no
reason believe in problems like that you are describing. I may be wrong,
but I would like to see facts, before banging my head.
If you believe the worker pool stack to be faulty, replace it with a
worker factory, that creates new workers all the time.
Jochen
