ssl broken pipe | connection reset by peer

[Achal Rastogi]

Hi,

Just checking to see if anyone is experiencing ssl connection failures
as well.

Here is the stack trace our logs are dumping out -

2009-06-07 22:28:38,263 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
2009-06-07 22:28:46,427 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- One or more input elements failed validation.
2009-06-07 22:28:51,836 ERROR [Thread-13486] (Message.java:541)-
java.io.IOException:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:
92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer
(OutputRecord.java:283)
at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:
272)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord
(SSLSocketImpl.java:666)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write
(AppOutputStream.java:59)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.axis.utils.ByteArray.writeTo(ByteArray.java:375)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:265)
at org.apache.axis.Message.writeTo(Message.java:539)
at org.apache.axis.transport.http.HTTPSender.writeToSocket
(HTTPSender.java:511)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
138)
at org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody16
(CriterionServiceSoapBindingStub.java:748)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody17$advice
(CriterionServiceSoapBindingStub.java:142)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
(CriterionServiceSoapBindingStub.java:1)
at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
158)
at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
(GoogleBidUploader.java:225)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSize
(GoogleBidUploader.java:197)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
(GoogleBidUploader.java:104)
at
com.ojos.server.sem.commandhandlers.ModifyAttributesGoogleSearch.execute
(ModifyAttributesGoogleSearch.java:31)
at com.ojos.framework.queue.NetServerThread.run(NetServerThread.java:
85)
2009-06-07 22:28:51,839 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
2009-06-07 22:28:58,955 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- One or more input elements failed validation.
2009-06-07 22:29:04,636 ERROR [Thread-13486] (Message.java:541)-
java.io.IOException:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:
92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer
(OutputRecord.java:283)
at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:
272)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord
(SSLSocketImpl.java:666)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write
(AppOutputStream.java:59)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.axis.utils.ByteArray.writeTo(ByteArray.java:375)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:265)
at org.apache.axis.Message.writeTo(Message.java:539)
at org.apache.axis.transport.http.HTTPSender.writeToSocket
(HTTPSender.java:511)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
138)
at org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody16
(CriterionServiceSoapBindingStub.java:748)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody17$advice
(CriterionServiceSoapBindingStub.java:142)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
(CriterionServiceSoapBindingStub.java:1)
at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
158)
at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
(GoogleBidUploader.java:225)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSize
(GoogleBidUploader.java:197)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
(GoogleBidUploader.java:104)
at
com.ojos.server.sem.commandhandlers.ModifyAttributesGoogleSearch.execute
(ModifyAttributesGoogleSearch.java:31)
at com.ojos.framework.queue.NetServerThread.run(NetServerThread.java:
85)
2009-06-07 22:29:04,639 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
2009-06-07 22:29:14,003 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- One or more input elements failed validation.
2009-06-07 22:29:19,480 ERROR [Thread-13486] (Message.java:541)-
java.io.IOException:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:
92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer
(OutputRecord.java:283)
at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:
272)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord
(SSLSocketImpl.java:666)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write
(AppOutputStream.java:59)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.axis.utils.ByteArray.writeTo(ByteArray.java:375)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:265)
at org.apache.axis.Message.writeTo(Message.java:539)
at org.apache.axis.transport.http.HTTPSender.writeToSocket
(HTTPSender.java:511)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
138)
at org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody16
(CriterionServiceSoapBindingStub.java:748)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody17$advice
(CriterionServiceSoapBindingStub.java:142)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
(CriterionServiceSoapBindingStub.java:1)
at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
158)
at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
(GoogleBidUploader.java:225)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSize
(GoogleBidUploader.java:197)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
(GoogleBidUploader.java:104)
at
com.ojos.server.sem.commandhandlers.ModifyAttributesGoogleSearch.execute
(ModifyAttributesGoogleSearch.java:31)
at com.ojos.framework.queue.NetServerThread.run(NetServerThread.java:
85)
2009-06-07 22:29:19,491 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
2009-06-07 22:29:24,895 ERROR [Thread-13486] (Message.java:541)-
java.io.IOException:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:
92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer
(OutputRecord.java:283)
at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:
272)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord
(SSLSocketImpl.java:666)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write
(AppOutputStream.java:59)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.apache.axis.utils.ByteArray.writeTo(ByteArray.java:375)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:265)
at org.apache.axis.Message.writeTo(Message.java:539)
at org.apache.axis.transport.http.HTTPSender.writeToSocket
(HTTPSender.java:511)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
138)
at org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody16
(CriterionServiceSoapBindingStub.java:748)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_aroundBody17$advice
(CriterionServiceSoapBindingStub.java:142)
at
com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
(CriterionServiceSoapBindingStub.java:1)
at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
158)
at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
(GoogleBidUploader.java:225)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSize
(GoogleBidUploader.java:197)
at
com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
(GoogleBidUploader.java:104)
at
com.ojos.server.sem.commandhandlers.ModifyAttributesGoogleSearch.execute
(ModifyAttributesGoogleSearch.java:31)
at com.ojos.framework.queue.NetServerThread.run(NetServerThread.java:
85)
2009-06-07 22:29:24,898 ERROR [Thread-13486] (GoogleBidUploader.java:
202)- javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Broken pipe

[tozor]

I saw this last night and again this morning. Different accounts each
time.

Tim Ozor

[Maxim]

We are seing it now too.

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody17$advice

> > (CriterionServiceSoapBindingStub.java:142)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
> > (CriterionServiceSoapBindingStub.java:1)
> >         at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
> > 158)
> >         at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
> > (GoogleBidUploader.java:225)
> >         at

> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSiz­e

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody17$advice

> > (CriterionServiceSoapBindingStub.java:142)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
> > (CriterionServiceSoapBindingStub.java:1)
> >         at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
> > 158)
> >         at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
> > (GoogleBidUploader.java:225)
> >         at

> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSiz­e

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a­roundBody17$advice

> > (CriterionServiceSoapBindingStub.java:142)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
> > (CriterionServiceSoapBindingStub.java:1)
> >         at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
> > 158)
> >         at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
> > (GoogleBidUploader.java:225)
> >         at

> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSiz­e

> > (GoogleBidUploader.java:197)
> >         at
> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
> > (GoogleBidUploader.java:104)
>

> ...
>
> read more »- Hide quoted text -
>
> - Show quoted text -

[Rob C.]

We had similar errors occur last night and this morning for both
report downloading and bid uploading on a number of different accounts
under a single MCC (using the same API token for all of them).

Rob Cooley

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody17$advice

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody17$advice

> > (CriterionServiceSoapBindingStub.java:142)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
> > (CriterionServiceSoapBindingStub.java:1)
> >         at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
> > 158)
> >         at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
> > (GoogleBidUploader.java:225)
> >         at
> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSiz e

> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody16
> > (CriterionServiceSoapBindingStub.java:748)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria_a roundBody17$advice

> > (CriterionServiceSoapBindingStub.java:142)
> >         at
> > com.google.api.adwords.v13.CriterionServiceSoapBindingStub.updateCriteria
> > (CriterionServiceSoapBindingStub.java:1)
> >         at com.ojos.server.sem.entity.AdWords.updateCriteria(AdWords.java:
> > 158)
> >         at com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryBatch
> > (GoogleBidUploader.java:225)
> >         at
> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.tryDifferentBatchSiz e
> > (GoogleBidUploader.java:197)
> >         at
> > com.ojos.server.semversiontwo.upload.GoogleBidUploader.updateBidsAtGoogle
> > (GoogleBidUploader.java:104)
>

> ...
>
> read more »

[AdWords API Advisor]

Hello All,

Given the multiple reports of similar behavior, I'm assuming that
this isn't just the normal one-off transient issues inherent in TCP
connections. I'll see what the core engineering team and our network
operations team has to say.

In the meantime, I have a feeling that they're going to ask for
information about source IP addresses and the timeframes during which
this occurred. This isn't the sort of info you'd want to post
publicly, so it's probably best to email adwordsa...@google.com
with that and any other log info you have. (Note for future readers of
this thread that we don't normally check that address for support
questions!)

Cheers,
-Jeff Posnick, AdWords API Team

> ...
>
> read more »

[Rori Stumpf]

FWIW, I have also been seeing this error over the last few days, but
not this morning.
Int32 Read(Byte[], Int32, Int32) throws "Received an unexpected EOF or
0 bytes from the transport stream."

C# Code:

Uri uri = new Uri(reportService.getReportDownloadUrl(reportId));
HttpWebRequest request = (HttpWebRequest)WebRequest.CreateDefault
(uri);

request.KeepAlive = false;
request.Method = "GET";
request.Timeout = 120000;

HttpWebResponse response = (HttpWebResponse)request.GetResponse();
Stream receiveStream = response.GetResponseStream();

fileStream = File.Create(fileNameDownloading);

int size = 1024 * 32;
byte[] writeData = new byte[size];
size = receiveStream.Read(writeData, 0, size);

while (size > 0)
{
fileStream.Write(writeData, 0, size);
size = receiveStream.Read(writeData, 0, size);
}
fileStream.Close();
receiveStream.Close();

Cheers,
Rori
http://www.SimpleSmartAds.com

On Jun 8, 4:49 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:

> Hello All,
>
>  Given the multiple reports of similar behavior, I'm assuming that
> this isn't just the normal one-off transient issues inherent in TCP
> connections. I'll see what the core engineering team and our network
> operations team has to say.
>
>  In the meantime, I have a feeling that they're going to ask for
> information about source IP addresses and the timeframes during which
> this occurred. This isn't the sort of info you'd want to post

> publicly, so it's probably best to email adwordsapiadvi...@google.com

> ...
>
> read more »

[Maxim]

The SSL handshake problem appeared to have been fixed in the evening
yesterday, but just started again.

[AdWords API Advisor]

Hello All,

We've collected IP and timestamp information from a number of
different developers and have passed it along to the team responsible
for our HTTP traffic. They're actively investigating the issue, but
I'm afraid that I can't point to a specific resolution to this issue
yet. I'll update this thread as I hear more.

Cheers,
-Jeff Posnick, AdWords API Team

[AdWords API Advisor]

Hello All,

I wanted to provide an update today, as we've heard word from several
developers that some of their HTTPS connections are still being closed
prematurely or are otherwise unsuccessful.

Our internal engineering team has not yet been able to track down a
root cause in our logs based on the IP and timestamp information that
we have. In the process of this investigation, they have identified a
few of our backend servers that are experiencing issues that, while
they are probably not the source of this issue, could have a negative
effect on the response times for a subset of AdWords API requests.
But, to reiterate, we're still actively trying to find the root cause
of the specific issues reported here.

Cheers,
-Jeff Posnick, AdWords API Team

On Jun 10, 10:43 am, AdWords API Advisor

[crosby]

Hi,
Experiencing similar issues, and have a bit more to add.
Even if i grab the download URL and paste it into a browser (firefox),
i'm getting failed downloads.


I'm using .NET (might be the only one, LOL), and
Systm.Net.WebClient.DownloadFile(url, fileName).
(I get the download URL from the API based on the report ID
immediately prior to downloading.)
This code has been running fine for months and is now failing
intermittently on random reports.
I get about 15 reports per day - everything in my MCC (so it is not a
case of bad report requests).

Jeff - thanks for your continued updates. I hope we can resolve this
soon.




On Jun 11, 3:17 pm, AdWords API Advisor <adwordsapiadvi...@google.com>

> > > yesterday, but just started again.- Hide quoted text -

[AdWords API Advisor]

Hello,

Yes, and I just wanted to check in today and let folks know that we
are aware that these issues continue for a number of developers and
investigation continues to be a priority. Unfortunately, our
engineering team is not seeing the sort of errors in our logs that
they'd expect given the reported issues, and that's complicating the
debugging process. We very much appreciate the cooperation of all
affected developers so far when it comes to passing along requested
debugging information, and if I hear that more specific information is
needed I'll follow up with individual requests.

Cheers,
-Jeff Posnick, AdWords API Team

[Rori Stumpf]

FWIW, I've been seeing this on larger files - in my case, the keyword
and ad performance reports.
I hope it's resolved soon..

Thanks,
Rori
http://www.SimpleSmartAds.com

On Jun 15, 12:14 pm, AdWords API Advisor

[AdWords API Advisor]

Hello All,

There is what I take to be a promising line of investigation that has
tracked down some spikes in SSL errors in our HTTP servers' logs that
may coincide with the issues everyone has been reporting. In order to
confirm that the newly-identified log entries are indicative of the
underlying root cause, I've been asked to gather one more round of
source IPs, timestamps with time zone, and destination URLs (in the
case of a report download) or AdWords API method names (in the case of
a SOAP call). These should correspond to instances in which your HTTPS
connection was terminated prematurely, similar to what was reported
upthread. The source IP should be the IP address that our webservers
see the request coming from, which might be the IP address of your
corporate network's HTTP proxy or gateway router.

The logs that show these errors apparently are very large and roll
over fairly quickly, so we'd need that information for requests that
are as recent as possible. If you could pass them along to
adwordsa...@google.com with "Connection Information" in the
subject line, that will help me track it down.

Thanks again for everyone's patience as we work through this issue,
and for your continued cooperation when it comes to providing
debugging information.

Cheers,
-Jeff Posnick, AdWords API Team

On Jun 15, 5:39 pm, Rori Stumpf <rstu...@gmail.com> wrote:
> FWIW, I've been seeing this on larger files - in my case, the keyword
> and ad performance reports.
> I hope it's resolved soon..
>
> Thanks,

> Rorihttp://www.SimpleSmartAds.com

[crosby]

Note that you can reproduce the error by attempting to download
an .xml report from AdWords web interface.
I'm getting corrupted report.xml.zip files when I download using the
AdWords Web interface using Mozilla FireFox.
e.g.: reportID 687352395, 687566415


Also able to reproduce by using the API Call:
getReportDownloadUrl(report.id)
and then cut/copy that into a browser location bar.


On Jun 16, 9:28 am, AdWords API Advisor <adwordsa...@google.com>
wrote:

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

[AdWords API Advisor]

Hello All,

Thanks to the folks who have passed along debugging information
related to failed HTTPS GETs of completed reports. Our engineering
team has matched up several of your requests in our web server logs
and continues to investigate why the data transfer might have been
prematurely ended.

One additional question: most of what we've been hearing about this
week are failures of HTTPS GETs for completed reports. Last week we
were hearing about people whose HTTPS POSTs failed when making SOAP
requests. Are folks still seeing failed HTTPS POSTs this week, and if
so, could you pass along the IP and timestamp info related to a failed
POST to the address mentioned upthread?

Cheers,
-Jeff Posnick, AdWords API Team

On Jun 16, 5:53 pm, crosby <cro...@justanswer.com> wrote:
> Note that you can reproduce the error by attempting to download
> an .xml report from AdWords web interface.
> I'm getting corrupted report.xml.zip files when I download using the
> AdWords Web interface using Mozilla FireFox.
> e.g.: reportID 687352395, 687566415
>
> Also able to reproduce by using the API Call:
> getReportDownloadUrl(report.id)
> and then cut/copy that into a browser location bar.
>

> On Jun 16, 9:28 am, AdWords API Advisor <adwordsapiadvi...@google.com>

> wrote:
>
>
>
> > Hello All,
>
> >  There is what I take to be a promising line of investigation that has
> > tracked down some spikes in SSL errors in our HTTP servers' logs that
> > may coincide with the issues everyone has been reporting. In order to
> > confirm that the newly-identified log entries are indicative of the
> > underlying root cause, I've been asked to gather one more round of
> > source IPs, timestamps with time zone, and destination URLs (in the
> > case of a report download) or AdWords API method names (in the case of
> > a SOAP call). These should correspond to instances in which your HTTPS
> > connection was terminated prematurely, similar to what was reported
> > upthread. The source IP should be the IP address that our webservers
> > see the request coming from, which might be the IP address of your
> > corporate network's HTTP proxy or gateway router.
>
> >  The logs that show these errors apparently are very large and roll
> > over fairly quickly, so we'd need that information for requests that
> > are as recent as possible. If you could pass them along to

> > adwordsapiadvi...@google.com with "Connection Information" in the

[AdWords API Advisor]

Hello All,

I wanted to reiterate that if you're still seeing issues with HTTPS
POSTs failing while making SOAP requests (like the issue at the very
start of this thread), we're very interested to hear about it and
gather their relevant debugging information (write to
adwordsa...@google.com with subject line "Connection
Information").

Unless we hear otherwise, we're going to assume that this issue is
only actively affecting HTTPS GET requests for completed reports.

Cheers,
-Jeff Posnick, AdWords API Team

On Jun 17, 6:00 pm, AdWords API Advisor <adwordsapiadvi...@google.com>

[crosby]

Seems to be fixed?
I've just successfully downloaded all of the reports in my MCC with
zero errors.
That's the first time I've been able to do that in about a week and a
half.

...awaiting official word that this is fixed ;-)

[Peer]

FYI: We have not seen the issue since June 16th.

[AdWords API Advisor]

Hello,

Well, it's definitely good to hear that these connection issues are
becoming less common. Based on my last conversation with an engineer
looking at our networking and web server setup, I don't think that
there's anything specific on our end that we did that could be
considered a "fix", per se, and I'm leaving the issue open for
continued investigation. So please do continue to let us know if and
when the problem recurs.

Cheers,
-Jeff Posnick, AdWords API Team

[crosby]

Hey Jeff,
Getting this error again.
Repeated failures on random reports at random times.
~Crosby

On Jun 19, 11:03 am, AdWords API Advisor

> > FYI: We have not seen the issue since June 16th.- Hide quoted text -

[lime98]

I'm seeing this error again as well.

-liem

[AdWords API Advisor]

Hello,

I'm sorry to hear that this is becoming an issue again. As before,
what I'd very much appreciate is if folks could write to
adwordsa...@google.com with the subject line "Connection Info"
and let us know what your source IP address is, the URL you're
requesting which fails, and a timestamp (with timezone) for that
request.

I'm assuming that the error reported back in your code is the same as
from previous occurrences?

Cheers,
-Jeff Posnick, AdWords API Team

[crosby]

Hi Jeff,
Will send Connection Info email later today.
I imagine many or even most of the other API users are NOT seeing this
issue...
Is there anything we can do along the lines being assigned to a
different bank of servers or something?
Thanks,
~Crosby

On Jul 6, 2:17 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:

> Hello,
>
>  I'm sorry to hear that this is becoming an issue again. As before,
> what I'd very much appreciate is if folks could write to

> adwordsapiadvi...@google.com with the subject line "Connection Info"

> and let us know what your source IP address is, the URL you're
> requesting which fails, and a timestamp (with timezone) for that
> request.
>
>  I'm assuming that the error reported back in your code is the same as
> from previous occurrences?
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Jul 6, 4:16 pm, lime98 <liem...@gmail.com> wrote:
>
>
>
> > I'm seeing this error again as well.
>

> > -liem- Hide quoted text -

[AdWords API Advisor]

Thanks, Crosby. The team responsible for investigating this sort of
issue should be able to determine which servers you're hitting based
on the connection info you provide, and if it appears that only
traffic destined for those machines is failing, I'm sure that they
would route folks away from them. It wasn't as simple as that based on
their previous investigations, however.

Cheers,
-Jeff Posnick, AdWords API Team