Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Business-PayPal-API CPAN distribution.

Report information
The Basics
Id: 105049
Status: resolved
Priority: 0/
Queue: Business-PayPal-API

People
Owner: Nobody in particular
Requestors: gregoa [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



From: gregoa [...] cpan.org
Subject: seems to use a dead API
We have the following bug reported to the Debian package of Business-PayPal-API (https://bugs.debian.org/787935): It doesn't seem to be a bug in the packaging, so you may want to take a look. Thanks! ------8<-----------8<-----------8<-----------8<-----------8<----- Package: libbusiness-paypal-api-perl Version: 0.70-1 Severity: normal Since a week ago, the paypal api service this module uses has been failing with 503 or 500. My guess is this means paypal has killed that API, presumably replacing it with a new API. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- see shy jo ------8<-----------8<-----------8<-----------8<-----------8<----- Thanks for considering, gregor herrmann, Debian Perl Group
On Sun Jun 07 13:00:23 2015, GREGOA wrote: Show quoted text
> We have the following bug reported to the Debian package of > Business-PayPal-API (https://bugs.debian.org/787935): > > It doesn't seem to be a bug in the packaging, so you may want to take > a look. Thanks! > > ------8<-----------8<-----------8<-----------8<-----------8<----- > > Package: libbusiness-paypal-api-perl > Version: 0.70-1 > Severity: normal > > Since a week ago, the paypal api service this module uses has been > failing with 503 or 500. My guess is this means paypal has killed that > API, presumably replacing it with a new API. > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) >
I'm not aware of PayPal deprecating an APIs in the recent past, but I'd also expect a 4xx error rather than a 5xx error in that case. There's not really much to go on with this ticket. Is it connecting to the sandbox or the production API? Which specific calls are failing? What (if any) status messages are being sent along with the HTTP error? Olaf
Subject: Re: [rt.cpan.org #105049] seems to use a dead API
Date: Mon, 15 Jun 2015 22:10:23 +0200
To: Olaf Alders via RT <bug-Business-PayPal-API [...] rt.cpan.org>
From: gregor herrmann <gregoa [...] debian.org>
On Mon, 15 Jun 2015 15:43:00 -0400, Olaf Alders via RT wrote: Show quoted text
Show quoted text
> > Since a week ago, the paypal api service this module uses has been > > failing with 503 or 500. My guess is this means paypal has killed that > > API, presumably replacing it with a new API.
Show quoted text
> I'm not aware of PayPal deprecating an APIs in the recent past, but I'd also expect a 4xx error rather than a 5xx error in that case. > > There's not really much to go on with this ticket. Is it connecting to the sandbox or the production API? Which specific calls are failing? What (if any) status messages are being sent along with the HTTP error?
Thanks for your reply, I've asked joeyh (the original submitter) to provide you with additional information. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Paco De Lucia, Al Di Meola, John Mc Laughlin: La Estiba
Download signature.asc
application/pgp-signature 949b

Message body not shown because it is not plain text.

I'm using the production API, with code and api keys that has been happily running for years (thanks for that!). Calling TransactionSearch with a StartDate and a TransactionID field. The error message looks like: 500 Can't connect to api-3t.paypal.com:443 at /usr/share/perl5/Business/PayPal/API.pm line 144.
On Tue Jun 16 10:44:37 2015, JOEY wrote: Show quoted text
> I'm using the production API, with code and api keys that has been > happily running for years (thanks for that!). Calling > TransactionSearch with a StartDate and a TransactionID field. > > The error message looks like: > > 500 Can't connect to api-3t.paypal.com:443 at > /usr/share/perl5/Business/PayPal/API.pm line 144.
Which version of Business::PayPal::API?
On Tue Jun 16 12:21:43 2015, OALDERS wrote: Show quoted text
> On Tue Jun 16 10:44:37 2015, JOEY wrote:
> > I'm using the production API, with code and api keys that has been > > happily running for years (thanks for that!). Calling > > TransactionSearch with a StartDate and a TransactionID field. > > > > The error message looks like: > > > > 500 Can't connect to api-3t.paypal.com:443 at > > /usr/share/perl5/Business/PayPal/API.pm line 144.
> > > Which version of Business::PayPal::API?
Also, have you ruled out network connectivity issues? That API is still supported: https://developer.paypal.com/docs/classic/api/endpoints/
On Tue Jun 16 12:29:48 2015, OALDERS wrote: Show quoted text
> On Tue Jun 16 12:21:43 2015, OALDERS wrote:
> > On Tue Jun 16 10:44:37 2015, JOEY wrote:
> > > I'm using the production API, with code and api keys that has been > > > happily running for years (thanks for that!). Calling > > > TransactionSearch with a StartDate and a TransactionID field. > > > > > > The error message looks like: > > > > > > 500 Can't connect to api-3t.paypal.com:443 at > > > /usr/share/perl5/Business/PayPal/API.pm line 144.
> > > > > > Which version of Business::PayPal::API?
> > Also, have you ruled out network connectivity issues? That API is > still supported: > > https://developer.paypal.com/docs/classic/api/endpoints/
Also, there are some pending SSL changes, but they should not (yet) cause any issues: https://ppmts.custhelp.com/app/answers/detail/a_id/1236
Actually I think that's a SSL bug if I turn on with use SOAP::Lite +trace => 'all'; use IO::Socket::SSL qw(debug4); I got SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH(0x7ff4bba2b148) SOAP::Transport::HTTP::Client::send_receive: POST https://api-3t.sandbox.paypal.com/2.0/ HTTP/1.1 Accept: text/xml Accept: multipart/* Accept: application/soap Content-Length: 1413 Content-Type: text/xml; charset=utf-8 SOAPAction: "urn:ebay:api:PayPalAPI#RequesterCredentials" <?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>app-middleware_api1.transfer-to.com</Username><Password>TNZ22QCNAWTRZUGB</Password><Signature>AJrq59CSdckv.51Q28hA02YHeyivAp34aeT5L17S5osNlLM2gjYUPTgl</Signature><Subject /></Credentials></RequesterCredentials></soap:Header><soap:Body><SetExpressCheckoutReq xmlns="urn:ebay:api:PayPalAPI"><SetExpressCheckoutRequest xsi:type="ns:SetExpressCheckoutRequestType"><Version xmlns="urn:ebay:apis:eBLBaseComponents" xsi:type="xs:string">3.0</Version><SetExpressCheckoutRequestDetails xmlns="urn:ebay:apis:eBLBaseComponents"><OrderTotal currencyID="USD" xmlns="urn:ebay:apis:eBLBaseComponents" xsi:type="cc:BasicAmountType">55.43</OrderTotal><ReturnURL xsi:type="xs:string">http://site.tld/return.html</ReturnURL><CancelURL xsi:type="xs:string">http://site.tld/canceltation.html</CancelURL><PaymentAction>Sale</PaymentAction></SetExpressCheckoutRequestDetails></SetExpressCheckoutRequest></SetExpressCheckoutReq></soap:Body></soap:Envelope> DEBUG: .../IO/Socket/SSL.pm:2649: new ctx 140689087512944 DEBUG: .../IO/Socket/SSL.pm:562: socket not yet connected DEBUG: ...18.4/Net/HTTPS.pm:68: local error: IO::Socket::IP configuration failed DEBUG: .../IO/Socket/SSL.pm:2682: free ctx 140689087512944 open=140689087512944 DEBUG: .../IO/Socket/SSL.pm:2687: free ctx 140689087512944 callback DEBUG: .../IO/Socket/SSL.pm:2694: OK free ctx 140689087512944 SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH(0x7ff4b9155050) SOAP::Transport::HTTP::Client::send_receive: 500 Can't connect to api-3t.sandbox.paypal.com:443 Content-Type: text/plain Client-Date: Wed, 12 Aug 2015 08:02:50 GMT Client-Warning: Internal response Can't connect to api-3t.sandbox.paypal.com:443 Operation timed out at /Users/fayland/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/LWP/Protocol/http.pm line 49. SOAP::Deserializer::deserialize: () SOAP::Parser::decode: () 500 Can't connect to api-3t.sandbox.paypal.com:443 at /Users/fayland/perl5/perlbrew/perls/perl-5.18.4/lib/site_perl/5.18.4/Business/PayPal/API.pm line 145. at test.pl line 23. upgrade IO::Socket::SSL and IP does not help. Thanks On Tue Jun 16 12:31:18 2015, OALDERS wrote: Show quoted text
> On Tue Jun 16 12:29:48 2015, OALDERS wrote:
> > On Tue Jun 16 12:21:43 2015, OALDERS wrote:
> > > On Tue Jun 16 10:44:37 2015, JOEY wrote:
> > > > I'm using the production API, with code and api keys that has > > > > been > > > > happily running for years (thanks for that!). Calling > > > > TransactionSearch with a StartDate and a TransactionID field. > > > > > > > > The error message looks like: > > > > > > > > 500 Can't connect to api-3t.paypal.com:443 at > > > > /usr/share/perl5/Business/PayPal/API.pm line 144.
> > > > > > > > > Which version of Business::PayPal::API?
> > > > Also, have you ruled out network connectivity issues? That API is > > still supported: > > > > https://developer.paypal.com/docs/classic/api/endpoints/
> > Also, there are some pending SSL changes, but they should not (yet) > cause any issues: > https://ppmts.custhelp.com/app/answers/detail/a_id/1236
Hello! I've got the exact same problem with anew installation of this module with perl 5.22.0. The old installation (with perl 5.20.1) works just fine, so it's not a problem with Paypal. Likely, but I'm not able to investigate it now, it's a problem with one of the SSL modules which SOAP::Lite uses. Anyway, all in all it seems this module is unusable in a new installation (I use the ExpressChekout API).
On Mon Sep 21 11:23:57 2015, ARTHAS wrote: Show quoted text
> Hello! > > I've got the exact same problem with anew installation of this module > with perl 5.22.0. The old installation (with perl 5.20.1) works just > fine, so it's not a problem with Paypal. > > Likely, but I'm not able to investigate it now, it's a problem with > one of the SSL modules which SOAP::Lite uses. > > Anyway, all in all it seems this module is unusable in a new > installation (I use the ExpressChekout API).
I believe the answer lies in this ticket: https://rt.cpan.org/Ticket/Display.html?id=107638 I'll fix this in master, but it's not in a releasable state right now. :( Try setting a non-zero timeout value when you create a new Business::PayPal::API object. my $foo = Business::PayPal::API->new( timeout => 30, ... ); Please let me know if this fixes it for you? Thanks, Olaf
On Thu Oct 08 21:54:03 2015, OALDERS wrote: Show quoted text
> On Mon Sep 21 11:23:57 2015, ARTHAS wrote:
> > Hello! > > > > I've got the exact same problem with anew installation of this module > > with perl 5.22.0. The old installation (with perl 5.20.1) works just > > fine, so it's not a problem with Paypal. > > > > Likely, but I'm not able to investigate it now, it's a problem with > > one of the SSL modules which SOAP::Lite uses. > > > > Anyway, all in all it seems this module is unusable in a new > > installation (I use the ExpressChekout API).
> > I believe the answer lies in this ticket: > > https://rt.cpan.org/Ticket/Display.html?id=107638 > > I'll fix this in master, but it's not in a releasable state right now. > :( > > Try setting a non-zero timeout value when you create a new > Business::PayPal::API object. > > my $foo = Business::PayPal::API->new( timeout => 30, ... ); > > Please let me know if this fixes it for you? > > Thanks, > > Olaf
Fixed in 0.72