[google-appengine] Re: App engiene change impacts my code ? Pls look into

2016-03-12 Thread Deepak Singh 
Facing business impact -

Code was working fine for last 2 years. No change in code but issue
persists. Does app engine change anything ?

Sending ---
response.setContentType("application/x-java-serialized-object");
response.setHeader("Content-Encoding", "gzip");
GZIPOutputStream gos = new GZIPOutputStream(response.getOutputStream());
ObjectOutputStream oos = new ObjectOutputStream(gos);
oos.writeObject(rs);
gos.finish();
oos.flush();
oos.close();


Reading ---

GZIPInputStream gi = new GZIPInputStream(new
ByteArrayInputStream(res.getContent()));
ObjectInputStream ois = new ObjectInputStream(gi);


Exception -
java.io.StreamCorruptedException: invalid stream header: 1F8B0800
at red color line

.

Pls help gae java team.



On Sat, Mar 12, 2016 at 11:49 PM, Deepak Singh 
wrote:

> Dear App engine team,
>
> For last couple of days, we are facing serialization issue. Our app does
> not add 'GZIP' header to response and thus we are getting the exception as
> below
>
>
> java.io.StreamCorruptedException: invalid stream header: 1F8B0800
>
>
> App id: pdstechi
>
> Pls resolve the same.
>
> The issue happens most frequently but not always.
>
>


-- 
Deepak Singh

-- 
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/CAF6cnzZ5mbpCdQxhuU%3DnfjjcGP0eKt-%3Dxi_GtYD8un247qaBBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

2016-03-12 Thread 'Adam (Cloud Platform Support)' via Google App Engine 
Hi Christian,

We've prodded the engineering team to update the issue trackers, so 
hopefully we will see some updates. The exception is Issue 6799 
 which was 
a years old report of slowness which is being closed out due to inactivity. 
Any new issues of that type should be filed as a new issue report.

On Tuesday, March 8, 2016 at 3:29:37 PM UTC-5, Christian F. Howes wrote:
>
> Hi Nick,
>
> Can you just review cloud support case 08706899 for which PIT issues are 
> not properly updated?  I've listed them out there in the original filing of 
> the case and the response from the support team is that several of them are 
> fixed.
>
> Thanks,
>
> Christian
>
> On Monday, March 7, 2016 at 11:15:49 AM UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Chris,
>>
>> If you could link which issues those are which have been fixed but not 
>> updated, we could take a look and determine whether they should be updated 
>> with any new relevant information, such as a fix. Feel free to reply to me 
>> in this thread.
>>
>> Best wishes,
>>
>> Nick
>>
>> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
>> wrote:
>>>
>>> Thanks Lorne. 
>>>
>>> Will we also be better at triaging and updating the Public Issue 
>>> Tracker?  Paid support told me today that several of the issues I filed 
>>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>>> be updated. 
>>>
>>> The lack of information provided, but the hard deadline on the turn-down 
>>> notice really concerns me as I don't have confidence that I will be able 
>>> to efficiently and effectively manage my app 6 weeks from now. 
>>>
>>> Thanks, 
>>>
>>> Christian 
>>>
>>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>>> feature 
>>> > parity in the Cloud Platform Console before turning down the Admin 
>>> Console. 
>>> >   The next communication we send will have more details and will 
>>> outline any 
>>> > gaps that exist and our plans to address them.  To answer the 
>>> questions 
>>> > asked here: 
>>> > 
>>> > - the dispatch rules will not be visible right away, but we are 
>>> actively 
>>> > working on a mechanism for you to view all of your App Engine 
>>> configuration 
>>> > in one place 
>>> > - prohibiting code downloads will not show up in the same way, but 
>>> this can 
>>> > be managed through roles and upcoming IAM functionality 
>>> > - as mentioned already, performance is a known issue that is a top 
>>> priority 
>>> > for the team 
>>> > 
>>> > Please continue to log issues as Nick mentioned and we will triage 
>>> > accordingly. 
>>> > 
>>> > Cheers, 
>>> > Lorne. 
>>> > 
>>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>>> >> 
>>> >> 1+ for speed. Also, is the requests/seconds coming to the new 
>>> console? At 
>>> >> least for me that's an easier value to discuss. Besides, the new 
>>> console's 
>>> >> request/minute do not match the request/second metric in the old 
>>> console. 
>>> >> 
>>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>>> wrote: 
>>> >>> 
>>> >>> +1 for the speed of the new console. The old console is very 
>>> noticeably 
>>> >>> faster. 
>>> >>> 
>>> >>> On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes 
>>> wrote: 
>>>  
>>>  Hi Lorne, 
>>>  
>>>  Is there any chance that you can share the console roadmap with us? 
>>>  given that we are getting the turn-down threats again, and the new 
>>> console 
>>>  is still missing many features it would be helpful to know which 
>>> ones are 
>>>  known to the team working on the console and which need new 
>>> tickets. 
>>>  
>>>  Is overall speed of the new console going to be addressed?  I lose 
>>>  several developer hours a week using the new console waiting for 
>>> things to 
>>>  load, and as such my team and I tend to use the old console 
>>> whenever 
>>>  possible. 
>>>  
>>>  Thanks, 
>>>  
>>>  Christian 
>>>  
>>>  On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman 
>>> wrote: 
>>> > 
>>> > I'm happy to report that both features are in the works and will 
>>> launch 
>>> > shortly, before the old console is turned down. 
>>> > 
>>> > Cheers, 
>>> > Lorne. 
>>> > 
>>> > 
>>> > On Tuesday, February 23, 2016 at 3:52:19 PM UTC-8, PK wrote: 
>>> >> 
>>> >> We also need the “Billing/Usage History” equivalent 
>>> functionality, has 
>>> >> this page been migrated to the new console? 
>>> >> 
>>> >> PK 
>>> >> p...@gae123.com 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> On Feb 23, 2016, at 3:46 PM, johnP  wrote: 
>>> >> 
>>> >> Just got email that old appengine console will be shut off in 6 
>>> weeks. 
>>> >>   The

[google-appengine] GAE Java is not adding response header for 'GZIP' / Content not 'GZIP'ped

2016-03-12 Thread Deepak Singh 
Dear App engine team,

For last couple of days, we are facing serialization issue. Our app does
not add 'GZIP' header to response and thus we are getting the exception as
below


java.io.StreamCorruptedException: invalid stream header: 1F8B0800


App id: pdstechi

Pls resolve the same.

The issue happens most frequently but not always.

-- 
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/CAF6cnzb59x83muEasUKK9Nrj2pUjDm2x_ixWnGz60WX2Nfmctg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Log Viewer - Unusable

2016-03-12 Thread pdknsk 
The issue with requests being broken up into several log entries was 
discussed some months ago.

https://groups.google.com/d/msg/google-appengine/aJhUMaVpYM8/StW2cjz7BgAJ

Perhaps the issue should be re-filed on the other bug tracker.

-- 
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/daa339e6-5b69-48de-9fa0-5a3587a5b035%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Content-Length response header

2016-03-12 Thread Linus Larsen 
It's a bit problematic, since we have our own CA cert and our clients sends 
encrypted packages (besides SSL). However these headers are 
what we get using http 1.0:

localhost:~$ curl -0 -I --cacert ~/cert/rootCA/rootCA.crt 
https://outlet.epspot.com/services/secure_outlet/hello
HTTP/1.0 200 OK
Content-Type: text/plain
Date: Sat, 12 Mar 2016 14:48:56 GMT
Server: Google Frontend
Alt-Svc: quic=":443"; ma=2592000; v="31,30,29,28,27,26,25"

This is what the clients are using (http POST)

HTTP/1.0 200 OK
Content-Type: application/octet-stream
Date: Sat, 12 Mar 2016 14:26:55 GMT
Server: Google Frontend
Cache-Control: private
Alt-Svc: quic=":443"; ma=2592000; v="31,30,29,28,27,26,25"
Accept-Ranges: none
Vary: Accept-Encoding

Using HTTP1.1 we get no Content-Length as well, however Content-Length were 
present before yesterday.

/ Linus

Den lördag 12 mars 2016 kl. 15:28:12 UTC+1 skrev Nickolas Daskalou:
>
> Hi Linus,
>
> Do you have a public URL we can test?
>
> Nick
> On 12/03/2016 10:07 PM, "Linus Larsen"  
> wrote:
>
>> Sometime yesterday (10th), our clients started to behave strage. After 
>> some investigation it seems like Google decided to remove the Content-Length
>> header from the http responses. The request / response messages between 
>> our clients are actually small protobuf encoded binary messages, using
>> Content-Type: application/octet-stream, and this has worked flawless 
>> uptil now.
>>
>> Ok, we thought we just set the clients to use HTTP1.0, since 
>> Content-Length header is mandatory in 1.0. But that didn't help we still 
>> don't get any 
>> Content-Length IMO this GAE behavior breaks GAE and HTTP1.0 compability.
>>
>> So, why is the Content-Length header missing? It was there before but has 
>> been removed, why wasn't we informed?
>>
>>
>>  
>>
>> -- 
>> 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/2d8c8dbb-8f93-4935-84ea-2bcc2f86de9f%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/b97cc796-e248-430f-97d7-5d065a244f5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Content-Length response header

2016-03-12 Thread Nickolas Daskalou 
Hi Linus,

Do you have a public URL we can test?

Nick
On 12/03/2016 10:07 PM, "Linus Larsen"  wrote:

> Sometime yesterday (10th), our clients started to behave strage. After
> some investigation it seems like Google decided to remove the Content-Length
> header from the http responses. The request / response messages between
> our clients are actually small protobuf encoded binary messages, using
> Content-Type: application/octet-stream, and this has worked flawless uptil
> now.
>
> Ok, we thought we just set the clients to use HTTP1.0, since
> Content-Length header is mandatory in 1.0. But that didn't help we still
> don't get any
> Content-Length IMO this GAE behavior breaks GAE and HTTP1.0 compability.
>
> So, why is the Content-Length header missing? It was there before but has
> been removed, why wasn't we informed?
>
>
>
>
> --
> 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/2d8c8dbb-8f93-4935-84ea-2bcc2f86de9f%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/CAOj3zuA%2BHiBZnLcfyqUkqbz8USAqUMe2PRokwwVQ44h0gz1uzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Content-Length response header

2016-03-12 Thread Linus Larsen 
Sometime yesterday (10th), our clients started to behave strage. After some 
investigation it seems like Google decided to remove the Content-Length
header from the http responses. The request / response messages between our 
clients are actually small protobuf encoded binary messages, using
Content-Type: application/octet-stream, and this has worked flawless uptil 
now.

Ok, we thought we just set the clients to use HTTP1.0, since Content-Length 
header is mandatory in 1.0. But that didn't help we still don't get any 
Content-Length IMO this GAE behavior breaks GAE and HTTP1.0 compability.

So, why is the Content-Length header missing? It was there before but has 
been removed, why wasn't we informed?


 

-- 
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/2d8c8dbb-8f93-4935-84ea-2bcc2f86de9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.