http://www.perlmonks.org?node_id=1225225


in reply to 500 timeout on paypal module
in thread paypal module

Hi, it would seem the next step would be to turn on debugging in the PayPal module. From the perldoc:
DEBUGGING You can see the raw SOAP XML sent and received by Business::PayPal::AP +I by setting its $Debug variable: $Business::PayPal::API::Debug = 1; $pp->SetExpressCheckout( %args ); this will print the XML being sent, and dump a Perl data structure of +the SOM received on STDERR (so check your error_log if running inside + a web server). If anyone knows how to turn a SOAP::SOM object into XML without settin +g outputxml(), let me know.

There is also a section in the perldoc on Error Handling. You might want to setup more error checking in your code to find the cause of the timeout.


I'm not really a human, but I play one on earth. ..... an animated JAPH

Replies are listed 'Best First'.
Re^2: 500 timeout on paypal module
by bigup401 (Pilgrim) on Nov 04, 2018 at 23:20 UTC

    after adding debug to 1. look wat i got LOL

    localhost [Sun Nov 04 18:13:50 2018] [error] [pid 628] mod_cgi.c(175): + [client 41.210.141.161:27391] AH01215: <?xml version="1.0" encoding= +"UTF-8"?><soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.or +g/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelop +e/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:x +sd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/20 +01/XMLSchema-instance"><soap:Header><RequesterCredentials soap:mustUn +derstand="1" xmlns="urn:ebay:api:PayPalAPI"><Credentials xmlns="urn:e +bay:apis:eBLBaseComponents"><Username>username</Username><Password>pa +ssword</Password><Signature /><Subject /></Credentials></RequesterCre +dentials></soap:Header><soap:Body><TransactionSearchReq xmlns="urn:eb +ay:api:PayPalAPI"><TransactionSearchRequest xsi:type="ns:TransactionS +earchRequestType"><Version xmlns="urn:ebay:apis:eBLBaseComponents" xs +i:type="xs:string">61.0</Version><StartDate xsi:nil="true" xsi:type=" +xs:dateTime" /><TransactionID xsi:type="xs:string">88343499343434</Tr +ansactionID></TransactionSearchRequest></TransactionSearchReq></soap: +Body></soap:Envelope>

      OK, so that request looks like this once it's been cleaned up ..

      <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soap:Header> <RequesterCredentials soap:mustUnderstand="1" xmlns="urn:ebay:api:PayPalAPI"> <Credentials xmlns="urn:ebay:apis:eBLBaseComponents"> <Username>username</Username> <Password>password</Password><Signature /> <Subject /> </Credentials> </RequesterCredentials> </soap:Header> <soap:Body> <TransactionSearchReq xmlns="urn:ebay:api:PayPalAPI"> <TransactionSearchRequest xsi:type="ns:TransactionSearchRequestType"> <Version xmlns="urn:ebay:apis:eBLBaseComponents" xsi:type="xs:string">61.0</Version> <StartDate xsi:nil="true" xsi:type="xs:dateTime" /> <TransactionID xsi:type="xs:string"> 88343499343434 </TransactionID> </TransactionSearchRequest> </TransactionSearchReq> </soap:Body> </soap:Envelope>
      This looks like the request that you were sending out. Not having used SOAP in about ten years, I don't know if this is properly formed, but it looks OK -- you're searching for a specific transaction by ID. Is it failing to send this request? Are you getting a response that you're not telling us about? Does this transaction really exist? Are your credentials valid?

      You need to show more work.

      Alex / talexb / Toronto

      Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.