Method:API Q&A

Re: Exception Caught: Could not connect to host

furrywombat — Thu, 14 Jan 2016 23:21:48 GMT

We fixed the issue by hosting the WSDL locally, but has reappeared. Emailed debug info to you. Hope we can get to the bottom of this...

Re: Exception Caught: Could not connect to host

furrywombat — Tue, 22 Dec 2015 03:47:26 GMT

Okay, now we're getting almost no connection whatsoever. 25-30 second latency, or no response whatsoever.

Re: Exception Caught: Could not connect to host

furrywombat — Mon, 21 Dec 2015 21:32:27 GMT

Thanks Jon!! Sending now...

Re: Exception Caught: Could not connect to host

Method_Jonathan — Mon, 21 Dec 2015 21:25:59 GMT

Furrywombat -

Please send me additional details via email (Request & Exception data) and I'll dig into the issue from our side.

Cheers

Jon

Exception Caught: Could not connect to host

furrywombat — Mon, 21 Dec 2015 15:51:00 GMT

We've struggled with this since day one with the API. Now we are having an issue with SELECT calls.

Received several failed connection attempts at various intervals over the weekend. Most of these are select calls made with the intention of cleaning up DB entries left over after transactions are deleted that could be messing with our report calculations. When I run into this problem, I can generally solve the issue by recreating the table from the Method UI. But I should not have to do that.

To be perfectly clear, we are able to load the WSDL into a PHP SoapClient object. That’s not where the connection error is happening… it’s happening when we attempt to request $soap->MethodAPISelect_XMLV2. Request, and exception data can be provided by email, but I am not posting it here.