Re: empty payload received from XML-RPC server

Hi Gaetano, 

Yes, you're totally right. It's the pear RPC class which has the issue
with time outs. What I did was to increase the time out limit on the
client side, and on the server side also. Everything works, even if it
takes up to 4-5 minutes. The rest is code optimization to make it
faster and avoid bottlenecks. 

No, no error was coming from the PEAR package, that's what made things
very confusing. So, increasing execution time limit is what fixes the
problem. I have a class wrapper for the PEAR xml-rpc class which now
also detects the timeout, so I won't have to deal with your pear code
(the app may be moved, and I wanted to keep everything in a single
repository without messing with too much 3rd party code).

Thanks for all the feedback mate!

Vladimir Ghetau
http://www.Vladimirated.com/

--- In [email protected], Gaetano Giunta <giunta.gaetano@...> wrote:
>
> Well, doh. I think I should have thought about that earlier.
> PHP script timeouts are quite common and quite annoying errors, as by 
> default there will be no hint about the timeout printed anywhere.
> So, if your webserver takes so long,
> - make sure that both php scripts can run for a good amount of time
(and 
> check memory_limit too, as I suspect the server page might be handling 
> quite a lot of stuff)
> - if it is just a plain socket timeout, I think that the pear client 
> should be able to handle it (line 1001 in RPC.php). did you check for 
> pear_error after calling send()?
> 
> Bye
> Gaetano
> 
> 
> > Hi G,
> >
> > Thanks for all the feedback, I managed to find out what's the problem.
> >
> > The XML-RPC PEAR package is ok, however, the XML-RPC server is not. It
> > needs a time out higher than 5 minutes in order to send over the
> > response details.
> >
> > That's odd, because no timout is sent from the XML-RPC class as an
> > error. I made some changes inside the code, and when the
> > XML_RPC_Client->send() method is used, a second argument (timeout,
> > int) can be passed to set the stream delay until the app timeouts.
> > That's where the empty headers list comes from and all the junk
> > following it.
> >
> > Thanks for your feedback. I think the PEAR::XML-RPC client package
> > needs some work at this time out level though.
> >
> > Thank you and happy holidays to everyone!
> >
> > Vladimir Ghetau
> > http://www.Vladimirated.com/ <http://www.Vladimirated.com/>
> >
> > --- In [email protected] <mailto:xml-rpc%40yahoogroups.com>, 
> > Gaetano Giunta <giunta.gaetano@> wrote:
> > >
> > > off the top of my head: there was a particular version of php that
> > broke
> > > support for HTTP_RAW_POST_DATA, which is used, iirc, by
pear::xmlrpc.
> > > Since you say it is only one server having this strange
problem... Try
> > > replacing that with php:input
> > >
> > >
> >
> >  
> 
> 
> 
> [Non-text portions of this message have been removed]
>




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/xml-rpc/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/