Intermittent HTTP 502 Bad Gateway when using AdWords API v10

[Bobby]

We have been receiving intermittent HTTP 502 Bad Gateway failures
since Monday 7/9 when using apility 1.10.3. The same call may succeed
one time and then fail the next. I am using a plain-vanilla apility
download with 1 bug fix we added in nusoap.php in order set the fault
flag true in order to be recognized by the calling apility google
object.

Is anybody else out there running into this problem? I just pulled
apility 1.9.0 and found the same problem occurs there also.

HTTP Error: Unsupported HTTP response status 502 Bad Gateway
(soapclientNusoap->response has contents of the response)

Any help is appreciated!

Cheers,
Bobby

[dk...@campusfood.com]

I am having the same issue with v10. I e-mailed API support about this
issue yesterday.

[AdWords API Advisor]

We believe this issue is resolved now. Please let me know if you see
any other 502 errors coming from us.

-Aaron Karp
AdWords API Team

On Jul 11, 3:15 pm, "dk...@campusfood.com" <dk...@campusfood.com>
wrote:

[Ryan Leavengood]

On 7/13/07, AdWords API Advisor <adwordsa...@google.com> wrote:
>
> We believe this issue is resolved now. Please let me know if you see
> any other 502 errors coming from us.

We have still been getting these intermittently all weekend and just
got another one. I am using v10 from Ruby with adwords4r (which I
implemented.) The method which we are using which sometimes gets this
error is getCriterionStats.

We have gotten a total of 13 of these since Friday, which certainly
isn't catastrophic, but I imagine the errors are annoying our users.

Regards,
Ryan

[AdWords API Advisor]

I'll make sure this issue gets picked up again. Thanks for reporting
it.

I'll update this thread when I know more.

-Aaron

On Jul 16, 1:59 pm, "Ryan Leavengood" <leaveng...@gmail.com> wrote:

[pete]

Hi Aaron - Any update on this issue as it is also affecting us (we use
a bespoke .Net client)?

If it's any help, IF the the problem occurs against a specific method
call for a specific account, then that call/account is repeatedly
affected, even when the same call for other accounts works fine.

At the moment, we are blindly retrying these calls which is a concern
as we have implemented some of the method calls as atomic "batches",
i,e if one fails, then all fail. Example would be a synchronise
process to ensure all listings at Google are in sync with our system.
Any failure during the process requires a complete retry.
Quota usage and hence cost, increases accordingly.

An update would really be appreciated.

Cheers

Pete

On Jul 16, 7:23 pm, AdWords API Advisor <adwordsapiadvi...@google.com>

wrote:
> I'll make sure this issue gets picked up again. Thanks for reporting
> it.
>
> I'll update this thread when I know more.
>
> -Aaron
>
> On Jul 16, 1:59 pm, "Ryan Leavengood" <leaveng...@gmail.com> wrote:
>
> > On 7/13/07, AdWords API Advisor <adwordsapiadvi...@google.com> wrote:
>
> > > We believe this issue is resolved now. Please let me know if you see

> > > any other502errors coming from us.

[AdWords API Advisor]

Hi Pete,

We're getting closer to a resolution, but nothing yet. There are
several engineers working right now to diagnose and fix the problem.
I'll update you again as soon as I know more.

-Aaron

[Rohit]

Pete:

We encountered the same problem and have a simple but reliable
workaround.
Most of the problems appear to be related to... getAllAds and
getAllCriteria

2007-07-17 13:14:53,284 ERROR [STDERR] (502)Bad Gateway
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:
744)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
32)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
2007-07-17 13:14:53,284 ERROR [STDERR] at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
2007-07-17 13:14:53,285 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2767)
2007-07-17 13:14:53,285 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2443)
2007-07-17 13:14:53,285 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2366)
2007-07-17 13:14:53,285 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:1812)
2007-07-17 13:14:53,285 ERROR [STDERR] at
com.google.api.adwords.AdServiceSoapBindingStub.getAllAds(AdServiceSoapBindingStub.java:
759)

2007-07-17 13:18:43,913 ERROR [STDERR] (502)Bad Gateway
2007-07-17 13:18:43,913 ERROR [STDERR] at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:
744)
2007-07-17 13:18:43,913 ERROR [STDERR] at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
2007-07-17 13:18:43,913 ERROR [STDERR] at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
32)
2007-07-17 13:18:43,913 ERROR [STDERR] at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2767)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2443)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:2366)
2007-07-17 13:18:43,914 ERROR [STDERR] at
org.apache.axis.client.Call.invoke(Call.java:1812)
2007-07-17 13:18:43,914 ERROR [STDERR] at
com.google.api.adwords.CriterionServiceSoapBindingStub.getAllCriteria(CriterionServiceSoapBindingStub.java:
518)

We wrap these calls in a 3-attempt retry block. So if a single call to
either of these API fail, we retry it rather than abort the entire
synchronization process.
For an account with about 50000 keywords, we run into this problem at
least 5 or 6 times.

Of course the bigger problem after making this fix in your system is
scheduling a push to production and aligning your release with Google
API updates, addressing these quirks, justifying to your managers why
this is needed, etc.

- Rohit

> > > Ryan- Hide quoted text -
>
> - Show quoted text -

[Erik]

Is there an update on this. I haven't escallated this through our
Google rep because you were aware of the problem, but this is taking
longer to fix than expected.

> com.google.api.adwords.AdServiceSoapBindingStub.getAllAds(AdServiceSoapBind­ingStub.java:

> com.google.api.adwords.CriterionServiceSoapBindingStub.getAllCriteria(Crite­rionServiceSoapBindingStub.java:

> > - Show quoted text -- Hide quoted text -

[AdWords API Advisor]

Hi Erik,

Our engineers are working on a resolution. It's been a slightly
elusive bug to find, but it should be fixed soon.

Sorry for not providing more frequent updates.

-Aaron

[Erik]

API team,

So, what is the status of this issue? We have clients who noticed we
didn't update their accounts in a timely manner and we would like to
be able to tell them this issue is closed.

The last ones I've seen were on 8/11, but there have been week long
lapses between these before.

Thanks,
Erik

On Jul 28, 12:07 pm, AdWords API Advisor

[AdWords API Advisor]

Hi Erik,

It's getting close to fixed, but still nothing yet. I promise I'll
update you guys as soon as I see a positive status update.

-Aaron