Hi,
We are making use of a configuration where the XMLRPC Server is brought
up in one linux server and the XMLRpc Client class is invoked in another
Linux Server(via a shell script and both are behind the firewall).The
XMLRPC server invokes a java business class and it runs for more than
one
Hi,
if your task actually requires more than one hour to run, I'd strongly
recommend an asynchronous procedure, like this:
- On the server, spawn a thread, which creates a unique ID. The new thread
starts performing the task and returns the ID to the client.
- Client starts running in a loop.
I agree, your communications would then be much more resistant to
network interruptions. And if the server and client each store the
unique ID (along with essential parameters), either could possibly be
shutdown and restarted and be able to resume the transaction.
-Ken
Jochen Wiedmann wrote:
I am continuing this from my bug post (sorry).
I am having difficulty with an array not being cast properly. I have done what
is outlined on here as far as I can tell.
http://ws.apache.org/xmlrpc/faq.html#arrays
This is the issue I opened for some background info
Hi,
you are right, there is a bug in FAQ.
the point is, that you can not cast the result of the XML RPC call, in your
case
return (String []) windows.getInstances(category);
is the problem.
You have to transform the result to String[] as described in the FAQ (but
without the cast in the first
You are right, Stan. Fixed!
On Tue, Oct 13, 2009 at 11:36 PM, Stanislav Miklik
stanislav.mik...@gmail.com wrote:
Hi,
you are right, there is a bug in FAQ.
the point is, that you can not cast the result of the XML RPC call, in your
case
return (String []) windows.getInstances(category);
Hi Jochen,
The setup is running in production for more than 1 year and we are
seeing the timeout behaviour only recently when the time of execution of
the server process is 1hr.Modifying the arch would be quite difficult
at this point.
I was looking at multiple layers and was little sceptic on
