[google-appengine] Re: Strange behaviour related to java Endpoints V2

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Þórir,

This is perfect as an issue report for the Public Issue Tracker 
, where we work with users to notify 
product teams and engineering of issues on the platform. Feel free to post 
this there and we'll be able to take a look. I can't say I've seen anything 
like this before. Be sure to include all the details given in this report. 
We may ask for you to reply to a private email we'll send if we require 
copies of the logs or your code.

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 31, 2017 at 8:07:18 AM UTC-4, Þórir Gunnarsson wrote:
>
> Hi
>
> Just wanted to check with the group if anyone is experiencing unusual 
> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
> standard environment.
>
> This morning we start getting reports from users where our Android client 
> is crashing a lot. Upon investigation we discover that yesterday 
> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
> look like this:
> /_ah/api/appendpoint/v8/users//dashboarddata
> and a HTTP 302 response according to the logs (this then results in a 
> crash in the Android client, which is a different story)
> On a regular day and most of the time this call from the client looks like 
> this.
> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>
> The strange thing here is the format of the log entry which is consistent 
> with the format of log entries after upgrading to endpoints v2. 
>
> We see the same exact Android client making this call and once in a while 
> it seems to get the new type of response (the endpoints v2 type log entry 
> and a 302).
>
> We did not deploy anything at this time yesterday and we were certainly 
> not using endpoints v2 at that time.
>
> After some testing we have now improved the situation by upgrading our 
> backend to using endpoints v2 (version 2.0.5). 
> I say improved because now most log entries look like they are coming from 
> endpoints v2 but once in a while we get the old style log entries and now 
> the old style log entries return 302 (according to server logs)
> The Android client no longer crashes but doesn't receive a response when 
> this happens.
>
> To further investigate what was happening we plugged in a http proxy to 
> see exactly what was going on.
> On a successful call there is a GET call to the server with a proper HTTP 
> 200 OK response
> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
> response and an "unsupportedProtocol" error.
> We don't see any difference between the two calls. The server logs tell us 
> that both are served by the same instance on the backend.
>
>  
> So is anyone experiencing something similar?
> Should we pin this on some Google update or possibly some misconfiguration 
> on our end?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/13dd22dd-d06e-49b2-bfe3-2cd79237ee95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Strange behaviour related to java Endpoints V2

[Þórir Gunnarsson]

I have created a public issue 
https://issuetracker.google.com/u/1/issues/36825521 but as the issue is now 
resolved after updating our SDK version and build tools to the latest 
versions the issue is more for informational purposes than something 
needing immediate attention.


On Friday, March 31, 2017 at 7:23:52 PM UTC, Nick (Cloud Platform Support) 
wrote:
>
> Hey Þórir,
>
> This is perfect as an issue report for the Public Issue Tracker 
> , where we work with users to notify 
> product teams and engineering of issues on the platform. Feel free to post 
> this there and we'll be able to take a look. I can't say I've seen anything 
> like this before. Be sure to include all the details given in this report. 
> We may ask for you to reply to a private email we'll send if we require 
> copies of the logs or your code.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Friday, March 31, 2017 at 8:07:18 AM UTC-4, Þórir Gunnarsson wrote:
>>
>> Hi
>>
>> Just wanted to check with the group if anyone is experiencing unusual 
>> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
>> standard environment.
>>
>> This morning we start getting reports from users where our Android client 
>> is crashing a lot. Upon investigation we discover that yesterday 
>> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
>> look like this:
>> /_ah/api/appendpoint/v8/users//dashboarddata
>> and a HTTP 302 response according to the logs (this then results in a 
>> crash in the Android client, which is a different story)
>> On a regular day and most of the time this call from the client looks 
>> like this.
>> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>>
>> The strange thing here is the format of the log entry which is consistent 
>> with the format of log entries after upgrading to endpoints v2. 
>>
>> We see the same exact Android client making this call and once in a while 
>> it seems to get the new type of response (the endpoints v2 type log entry 
>> and a 302).
>>
>> We did not deploy anything at this time yesterday and we were certainly 
>> not using endpoints v2 at that time.
>>
>> After some testing we have now improved the situation by upgrading our 
>> backend to using endpoints v2 (version 2.0.5). 
>> I say improved because now most log entries look like they are coming 
>> from endpoints v2 but once in a while we get the old style log entries and 
>> now the old style log entries return 302 (according to server logs)
>> The Android client no longer crashes but doesn't receive a response when 
>> this happens.
>>
>> To further investigate what was happening we plugged in a http proxy to 
>> see exactly what was going on.
>> On a successful call there is a GET call to the server with a proper HTTP 
>> 200 OK response
>> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
>> response and an "unsupportedProtocol" error.
>> We don't see any difference between the two calls. The server logs tell 
>> us that both are served by the same instance on the backend.
>>
>>  
>> So is anyone experiencing something similar?
>> Should we pin this on some Google update or possibly some 
>> misconfiguration on our end?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7d279068-7bf3-43ee-a23c-2744e9c169a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Strange behaviour related to java Endpoints V2

[Teke Sawo]

I am experiencing the same issue.

Do we find any solution?

On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þórir Gunnarsson wrote:
>
> Hi
>
> Just wanted to check with the group if anyone is experiencing unusual 
> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
> standard environment.
>
> This morning we start getting reports from users where our Android client 
> is crashing a lot. Upon investigation we discover that yesterday 
> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
> look like this:
> /_ah/api/appendpoint/v8/users//dashboarddata
> and a HTTP 302 response according to the logs (this then results in a 
> crash in the Android client, which is a different story)
> On a regular day and most of the time this call from the client looks like 
> this.
> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>
> The strange thing here is the format of the log entry which is consistent 
> with the format of log entries after upgrading to endpoints v2. 
>
> We see the same exact Android client making this call and once in a while 
> it seems to get the new type of response (the endpoints v2 type log entry 
> and a 302).
>
> We did not deploy anything at this time yesterday and we were certainly 
> not using endpoints v2 at that time.
>
> After some testing we have now improved the situation by upgrading our 
> backend to using endpoints v2 (version 2.0.5). 
> I say improved because now most log entries look like they are coming from 
> endpoints v2 but once in a while we get the old style log entries and now 
> the old style log entries return 302 (according to server logs)
> The Android client no longer crashes but doesn't receive a response when 
> this happens.
>
> To further investigate what was happening we plugged in a http proxy to 
> see exactly what was going on.
> On a successful call there is a GET call to the server with a proper HTTP 
> 200 OK response
> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
> response and an "unsupportedProtocol" error.
> We don't see any difference between the two calls. The server logs tell us 
> that both are served by the same instance on the backend.
>
>  
> So is anyone experiencing something similar?
> Should we pin this on some Google update or possibly some misconfiguration 
> on our end?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/01921515-8737-49bd-9f6e-2cb4cd2a057c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Strange behaviour related to java Endpoints V2

[Þórir Gunnarsson]

Hi

This stopped being an issue for us after updating the backend to use 
Endpoints V2. We never really figured out exactly what caused the issue in 
the first place.

ÞG


On Monday, June 26, 2017 at 1:47:24 PM UTC, Teke Sawo wrote:
>
> I am experiencing the same issue.
>
> Do we find any solution?
>
> On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þórir Gunnarsson wrote:
>>
>> Hi
>>
>> Just wanted to check with the group if anyone is experiencing unusual 
>> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
>> standard environment.
>>
>> This morning we start getting reports from users where our Android client 
>> is crashing a lot. Upon investigation we discover that yesterday 
>> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
>> look like this:
>> /_ah/api/appendpoint/v8/users//dashboarddata
>> and a HTTP 302 response according to the logs (this then results in a 
>> crash in the Android client, which is a different story)
>> On a regular day and most of the time this call from the client looks 
>> like this.
>> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>>
>> The strange thing here is the format of the log entry which is consistent 
>> with the format of log entries after upgrading to endpoints v2. 
>>
>> We see the same exact Android client making this call and once in a while 
>> it seems to get the new type of response (the endpoints v2 type log entry 
>> and a 302).
>>
>> We did not deploy anything at this time yesterday and we were certainly 
>> not using endpoints v2 at that time.
>>
>> After some testing we have now improved the situation by upgrading our 
>> backend to using endpoints v2 (version 2.0.5). 
>> I say improved because now most log entries look like they are coming 
>> from endpoints v2 but once in a while we get the old style log entries and 
>> now the old style log entries return 302 (according to server logs)
>> The Android client no longer crashes but doesn't receive a response when 
>> this happens.
>>
>> To further investigate what was happening we plugged in a http proxy to 
>> see exactly what was going on.
>> On a successful call there is a GET call to the server with a proper HTTP 
>> 200 OK response
>> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
>> response and an "unsupportedProtocol" error.
>> We don't see any difference between the two calls. The server logs tell 
>> us that both are served by the same instance on the backend.
>>
>>  
>> So is anyone experiencing something similar?
>> Should we pin this on some Google update or possibly some 
>> misconfiguration on our end?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1af397de-0d94-4aec-b267-597e9e6961ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Strange behaviour related to java Endpoints V2

[Teke Sawo]

Hi

I have been developing with python. I updated to Endpoint version 2.0.6 
following guide from here. 

 
But the issue is not fixed.

On Monday, June 26, 2017 at 4:56:00 PM UTC+3, Þórir Gunnarsson wrote:
>
> Hi
>
> This stopped being an issue for us after updating the backend to use 
> Endpoints V2. We never really figured out exactly what caused the issue in 
> the first place.
>
> ÞG
>
>
> On Monday, June 26, 2017 at 1:47:24 PM UTC, Teke Sawo wrote:
>>
>> I am experiencing the same issue.
>>
>> Do we find any solution?
>>
>> On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þórir Gunnarsson wrote:
>>>
>>> Hi
>>>
>>> Just wanted to check with the group if anyone is experiencing unusual 
>>> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
>>> standard environment.
>>>
>>> This morning we start getting reports from users where our Android 
>>> client is crashing a lot. Upon investigation we discover that yesterday 
>>> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
>>> look like this:
>>> /_ah/api/appendpoint/v8/users//dashboarddata
>>> and a HTTP 302 response according to the logs (this then results in a 
>>> crash in the Android client, which is a different story)
>>> On a regular day and most of the time this call from the client looks 
>>> like this.
>>> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>>>
>>> The strange thing here is the format of the log entry which is 
>>> consistent with the format of log entries after upgrading to endpoints v2. 
>>>
>>> We see the same exact Android client making this call and once in a 
>>> while it seems to get the new type of response (the endpoints v2 type log 
>>> entry and a 302).
>>>
>>> We did not deploy anything at this time yesterday and we were certainly 
>>> not using endpoints v2 at that time.
>>>
>>> After some testing we have now improved the situation by upgrading our 
>>> backend to using endpoints v2 (version 2.0.5). 
>>> I say improved because now most log entries look like they are coming 
>>> from endpoints v2 but once in a while we get the old style log entries and 
>>> now the old style log entries return 302 (according to server logs)
>>> The Android client no longer crashes but doesn't receive a response when 
>>> this happens.
>>>
>>> To further investigate what was happening we plugged in a http proxy to 
>>> see exactly what was going on.
>>> On a successful call there is a GET call to the server with a proper 
>>> HTTP 200 OK response
>>> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
>>> response and an "unsupportedProtocol" error.
>>> We don't see any difference between the two calls. The server logs tell 
>>> us that both are served by the same instance on the backend.
>>>
>>>  
>>> So is anyone experiencing something similar?
>>> Should we pin this on some Google update or possibly some 
>>> misconfiguration on our end?
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/09ec25c9-8016-4b04-998f-5a444508758f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Strange behaviour related to java Endpoints V2

['Dan Ciruli' via Google App Engine]

We are investigating and will report back findings here.

On Jun 26, 2017 6:56 AM, "Þórir Gunnarsson" 
wrote:

> Hi
>
> This stopped being an issue for us after updating the backend to use
> Endpoints V2. We never really figured out exactly what caused the issue in
> the first place.
>
> ÞG
>
>
> On Monday, June 26, 2017 at 1:47:24 PM UTC, Teke Sawo wrote:
>>
>> I am experiencing the same issue.
>>
>> Do we find any solution?
>>
>> On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þórir Gunnarsson wrote:
>>>
>>> Hi
>>>
>>> Just wanted to check with the group if anyone is experiencing unusual
>>> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine
>>> standard environment.
>>>
>>> This morning we start getting reports from users where our Android
>>> client is crashing a lot. Upon investigation we discover that yesterday
>>> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that
>>> look like this:
>>> /_ah/api/appendpoint/v8/users//dashboarddata
>>> and a HTTP 302 response according to the logs (this then results in a
>>> crash in the Android client, which is a different story)
>>> On a regular day and most of the time this call from the client looks
>>> like this.
>>> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>>>
>>> The strange thing here is the format of the log entry which is
>>> consistent with the format of log entries after upgrading to endpoints v2.
>>>
>>> We see the same exact Android client making this call and once in a
>>> while it seems to get the new type of response (the endpoints v2 type log
>>> entry and a 302).
>>>
>>> We did not deploy anything at this time yesterday and we were certainly
>>> not using endpoints v2 at that time.
>>>
>>> After some testing we have now improved the situation by upgrading our
>>> backend to using endpoints v2 (version 2.0.5).
>>> I say improved because now most log entries look like they are coming
>>> from endpoints v2 but once in a while we get the old style log entries and
>>> now the old style log entries return 302 (according to server logs)
>>> The Android client no longer crashes but doesn't receive a response when
>>> this happens.
>>>
>>> To further investigate what was happening we plugged in a http proxy to
>>> see exactly what was going on.
>>> On a successful call there is a GET call to the server with a proper
>>> HTTP 200 OK response
>>> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND
>>> response and an "unsupportedProtocol" error.
>>> We don't see any difference between the two calls. The server logs tell
>>> us that both are served by the same instance on the backend.
>>>
>>>
>>> So is anyone experiencing something similar?
>>> Should we pin this on some Google update or possibly some
>>> misconfiguration on our end?
>>>
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/1af397de-0d94-4aec-b267-
> 597e9e6961ea%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJ6Lt08baTzM3mxFD7qZnhox%3DjwGp4o%3DGuwzB0bbOWDSBdp6vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Strange behaviour related to java Endpoints V2

[Teke Sawo]

Any updates?

On Monday, June 26, 2017 at 6:21:00 PM UTC+3, Dan Ciruli wrote:
>
> We are investigating and will report back findings here. 
>
> On Jun 26, 2017 6:56 AM, "Þórir Gunnarsson"  > wrote:
>
>> Hi
>>
>> This stopped being an issue for us after updating the backend to use 
>> Endpoints V2. We never really figured out exactly what caused the issue in 
>> the first place.
>>
>> ÞG
>>
>>
>> On Monday, June 26, 2017 at 1:47:24 PM UTC, Teke Sawo wrote:
>>>
>>> I am experiencing the same issue.
>>>
>>> Do we find any solution?
>>>
>>> On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þórir Gunnarsson wrote:

 Hi

 Just wanted to check with the group if anyone is experiencing unusual 
 behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
 standard environment.

 This morning we start getting reports from users where our Android 
 client is crashing a lot. Upon investigation we discover that yesterday 
 (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
 look like this:
 /_ah/api/appendpoint/v8/users//dashboarddata
 and a HTTP 302 response according to the logs (this then results in a 
 crash in the Android client, which is a different story)
 On a regular day and most of the time this call from the client looks 
 like this.
 /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData

 The strange thing here is the format of the log entry which is 
 consistent with the format of log entries after upgrading to endpoints v2. 

 We see the same exact Android client making this call and once in a 
 while it seems to get the new type of response (the endpoints v2 type log 
 entry and a 302).

 We did not deploy anything at this time yesterday and we were certainly 
 not using endpoints v2 at that time.

 After some testing we have now improved the situation by upgrading our 
 backend to using endpoints v2 (version 2.0.5). 
 I say improved because now most log entries look like they are coming 
 from endpoints v2 but once in a while we get the old style log entries and 
 now the old style log entries return 302 (according to server logs)
 The Android client no longer crashes but doesn't receive a response 
 when this happens.

 To further investigate what was happening we plugged in a http proxy to 
 see exactly what was going on.
 On a successful call there is a GET call to the server with a proper 
 HTTP 200 OK response
 On a failure there is a GET call to the server with a HTTP 404 NOT 
 FOUND response and an "unsupportedProtocol" error.
 We don't see any difference between the two calls. The server logs tell 
 us that both are served by the same instance on the backend.

  
 So is anyone experiencing something similar?
 Should we pin this on some Google update or possibly some 
 misconfiguration on our end?


 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/1af397de-0d94-4aec-b267-597e9e6961ea%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e4512b25-737b-4d34-859c-509183ec0281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.