Hi Santhosh, I was able to make that request without receiving 502 errors. Do you find that the errors are limited to certain ad groups? I've noticed that this account is very large, and it could be that for some ad groups the results may be too large to be returned in a single response. One of the nice features about the v2009 API is the ability to specify paging, so large requests can be broken into smaller ones: http://code.google.com/apis/adwords/v2009/docs/reference/AdGroupCriterionService.AdGroupCriterionSelector.html#paging.
Best, - Eric On Nov 3, 5:43 pm, Santhosh Nair <snai...@gmail.com> wrote: > Hi Eric, > Here is a sample API call that Failed. We didn't get any response > back apart from the "Bad Gateway/502" error. > As I mentioned, we keep trying even after the failure and it may work > for a while. We were not able to download the entire campaign data > yet. Please let me know if this help you identify the problem. > thanks > Santhosh > --------------------- > <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> > <env:Header> > <G:useragent xmlns:G='https://adwords.google.com/api/adwords/ > v13'>XXX</G:useragent> > <G:developerToken xmlns:G='https://adwords.google.com/api/adwords/ > v13'>xxx</G:developerToken> > <G:applicationToken xmlns:G='https://adwords.google.com/api/adwords/ > v13'>xxx</G:applicationToken> > <G:email xmlns:G='https://adwords.google.com/api/adwords/v13'>xxx</ > G:email> > <G:password xmlns:G='https://adwords.google.com/api/adwords/ > v13'>xxx</G:password> > </env:Header> > <env:Body> > <getAllCriteria xmlns='https://adwords.google.com/api/adwords/v13'> > <adGroupId>1241093xxx</adGroupId> > </getAllCriteria> > </env:Body> > </env:Envelope> > > On Nov 3, 9:08 am, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > > > Hi Santhosh, > > > The account appears to be in good standing, and I was able to make > > some requests against it without a problem. Can you please provide > > the SOAP XML for a specific request which fails? > > > Best, > > - Eric > > > On Oct 29, 7:38 pm, Santhosh Nair <snai...@gmail.com> wrote: > > > > Hi Eric, > > > I emailed the customer id > > > > thanks, > > > Santhosh > > > > On Oct 29, 7:21 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > > wrote: > > > > > Hi Santhosh, > > > > > In order to further troubleshoot the problem I will need to get the > > > > customer ID for this account. Please don't post it to the forum, but > > > > instead email me the information at adwordsapiadvi...@google.com. > > > > > Best, > > > > - Eric > > > > > On Oct 28, 6:28 pm, Santhosh Nair <snai...@gmail.com> wrote: > > > > > > Thanks Eric. It looks like the error occours randomly (on this > > > > > particular account) . API returned these errors while retrieving list > > > > > of Keywords as well as Ads. > > > > > This error is easily reproducible on this account. It is been 5 days > > > > > since we tried to download campaign data, it fails even after more > > > > > than 100 retries. > > > > > > regards, > > > > > Santhosh > > > > > > On Oct 28, 7:37 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > > > > wrote: > > > > > > > Hi Santhosh, > > > > > > > 502 errors are usually returned when a timeout has occurred between > > > > > > internal Google servers. Are you noticing that there certain > > > > > > services > > > > > > or method that are triggering this error? Is the error consistent > > > > > > or > > > > > > reproducible? > > > > > > > Best, > > > > > > - Eric > > > > > > > On Oct 27, 8:22 pm, Santhosh Nair <snai...@gmail.com> wrote: > > > > > > > > Hello Eric, > > > > > > > Thank you for you response. We do not experience any network > > > > > > > issues > > > > > > > and in fact API access to all other accounts (to other seach > > > > > > > engines > > > > > > >too) works with out errors. > > > > > > > Here is the stack trace from last exception. Please let's know > > > > > > > whether > > > > > > > some particular accounts may experienceconnectionissues at this > > > > > > > moment. > > > > > > > > org.jboss.remoting.CannotConnectException: Can not connect http > > > > > > > client > > > > > > > invoker. Invalid HTTP server response > > > > > > > [502] - Bad Gateway. Response: Bad Gateway/502. > > > > > > > at > > > > > > > org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection > > > > > > > (HTTPClientInvoker.java:368) > > > > > > > at org.jboss.remoting.transport.http.HTTPClientInvoker.transport > > > > > > > (HTTPClientInvoker.java:148) > > > > > > > at org.jboss.remoting.MicroRemoteClientInvoker.invoke > > > > > > > (MicroRemoteClientInvoker.java:141) > > > > > > > at org.jboss.remoting.Client.invoke(Client.java:1858) > > > > > > > at org.jboss.remoting.Client.invoke(Client.java:718) > > > > > > > at org.jboss.ws.core.client.RemotingConnectionImpl.invoke > > > > > > > (RemotingConnectionImpl.java:190) > > > > > > > ... 94 more > > > > > > > Caused by: org.jboss.ws.WSException: Invalid HTTP server response > > > > > > > [502] - Bad Gateway > > > > > > > at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read > > > > > > > (SOAPMessageUnMarshaller.java:77) > > > > > > > at > > > > > > > org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse > > > > > > > (HTTPClientInvoker.java:548) > > > > > > > at > > > > > > > org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection > > > > > > > (HTTPClientInvoker.java:322) > > > > > > > ... 99 more > > > > > > > > thanks, > > > > > > > Santhosh -- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
