[google-appengine] Re: Javaland scheduler behavior

[Mauricio Aristizabal]

I'm experiencing the same issues and it's a shame: It feels like Google 
designed an F1 race car here, and then limited top speed to 20mph.
>
>
What good is this shiny platform, full of slick, ready-to-use APIs and the 
promise of automatic elasticity, if a simple page often takes 40 seconds to 
load, and there is little you can do about it?

Further this doesn't seem like a complex algorithm but a simple rule: don't 
add any request to a new instance's queue until the warmup request returns 
(and it is marked available / added to the pool).

I really, really, hope this is a bug that will be addressed soon (and that 
release processes are improved so others like it are never introduced).

Either way, unfortunately between this and the last few days' issues AE is 
not looking very enterprise-ready at all, and I now have to consider it a 
risk rather than a highlight in my business plan and investor pitch.

Mauricio
Founder, 
commentous.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/xb_z-YfvbMgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Need some info related to speckle

[Vivek More]

Hi,

I read somewhere that we can use *speckle* to communicate to local database
instance is it true?
If yes, please provide me some reference material so that I can look more
into it.

I am not able to find any reference material related to this on net.

Thanks,
Vivek

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

RE: [google-appengine] Re: Do maintentance periods really have to be during core working hours?

[Brandon Wirtz]

I chose M/S because even more than a mermaid, I want a girl in a Dominatrix
outfit.

(I got the pool, so I'm one step closer on the Mermaid thing)



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Do maintentance periods really have to be during core working hours?

[Greg]

Just a reminder that "core working hours" for many of us are different
from yours. Back when we were on MS, it seemed like every outage was
in New Zealand working hours. Basically Google get it in the neck from
somewhere around the globe no matter when they schedule their
maintenance.

And the real answer to your problem is... HR. If you care about your
app enough to complain about outages, you should make migrating to HR
your top priority. It will change your life, really - no more clenched
guts when you get an email about the next maintenance period, or
bitten fingernails when they go over the scheduled time. Plus you get
to make snide comments to MS-users like this... :)

Cheers!
Greg.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: using GAE with javascript

[Ikai Lan (Google)]

For raw access, pretty much the barrier is demand. There's some argument
for raw datastore access via Javascript, but then there are all kinds of
messy business logic and security that you'd have to specify anyway.

Unless you are just talking about using HTML5 and Javascript to talk to
Python/Java/Go. You can do that today. But odds are good you don't want to
give unfettered access to every single user of your application. That's why
you write the Python/Java/Go code: to implement the business logic.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 7:03 PM, that an  wrote:

> Thanks for the link.  I really appreciate the response straight from
> the source.  And it helps confirm for me that I'm probably looking for
> something that doesn't yet exist.
>
> But what is the barrier for Google providing access to GAE via
> javascript?
>
> GWT is, after all, converted to javascript when it is running on the
> client - so it is technically possible.  And communication between
> client and server, no matter what platform they use is standard HTTP
> protocol - neither client or server really cares (or should care)
> about how the other is implemented.
>
> I'm not trying to be obtuse, but it just seems like such a...
> natural... fit and obvious gap in the simplicity of the development.
> Write your GAE server in a natural server side language like Python or
> Java, and write your client in a natural client side language like
> javascript and HTML5.
>
> Is there a reason that I've missed?  Help me out here - I just don't
> understand the omission...
>
>
> On Mar 14, 1:40 pm, "Ikai Lan (Google)"  wrote:
> > I wouldn't say dancing - we just don't provide that kind of access. Even
> if
> > we ever did in the future, we would likely wrap an auth layer around it
> > (probably OAuth 2.0).
> >
> > This might be the closest thing you are looking for:
> >
> > http://code.google.com/p/google-protorpc/
> >
> > But I don't have any thoughts about security, and you'd have to write the
> > code yourself to translate requests to datastore calls.
> >
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> > plus.ikailan.com
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Mar 12, 2012 at 8:31 PM, that an  wrote:
> > > I'm looking for a way to use javascript code to directly interface
> > > with the google app engine and with the datastore.
> >
> > > I've already used the GWT/GAE Java SDK in Eclipse with varying levels
> > > of success, but I'm looking for a way to leverage the benefits of GAE
> > > cloud services with the direct DOM manipulation of writing javascript
> > > directly for the client.  GWT front end just doesn't seem flexible
> > > enough to do what javascript can.
> >
> > > Maybe I've missed something obvious, or something that is out there
> > > does it, but I've been searching for awhile now, and it just seems
> > > like Google is dancing around any direct client access to their App
> > > Engine and cloud datastore.
> >
> > > I've pretty much exhausted my leads so far - Any direction is greatly
> > > appreciated.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine" group.
> > > To post to this group, send email to google-appengine@googlegroups.com
> .
> > > To unsubscribe from this group, send email to
> > > google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: using GAE with javascript

[that an]

Thanks for the link.  I really appreciate the response straight from
the source.  And it helps confirm for me that I'm probably looking for
something that doesn't yet exist.

But what is the barrier for Google providing access to GAE via
javascript?

GWT is, after all, converted to javascript when it is running on the
client - so it is technically possible.  And communication between
client and server, no matter what platform they use is standard HTTP
protocol - neither client or server really cares (or should care)
about how the other is implemented.

I'm not trying to be obtuse, but it just seems like such a...
natural... fit and obvious gap in the simplicity of the development.
Write your GAE server in a natural server side language like Python or
Java, and write your client in a natural client side language like
javascript and HTML5.

Is there a reason that I've missed?  Help me out here - I just don't
understand the omission...


On Mar 14, 1:40 pm, "Ikai Lan (Google)"  wrote:
> I wouldn't say dancing - we just don't provide that kind of access. Even if
> we ever did in the future, we would likely wrap an auth layer around it
> (probably OAuth 2.0).
>
> This might be the closest thing you are looking for:
>
> http://code.google.com/p/google-protorpc/
>
> But I don't have any thoughts about security, and you'd have to write the
> code yourself to translate requests to datastore calls.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
>
>
>
>
> On Mon, Mar 12, 2012 at 8:31 PM, that an  wrote:
> > I'm looking for a way to use javascript code to directly interface
> > with the google app engine and with the datastore.
>
> > I've already used the GWT/GAE Java SDK in Eclipse with varying levels
> > of success, but I'm looking for a way to leverage the benefits of GAE
> > cloud services with the direct DOM manipulation of writing javascript
> > directly for the client.  GWT front end just doesn't seem flexible
> > enough to do what javascript can.
>
> > Maybe I've missed something obvious, or something that is out there
> > does it, but I've been searching for awhile now, and it just seems
> > like Google is dancing around any direct client access to their App
> > Engine and cloud datastore.
>
> > I've pretty much exhausted my leads so far - Any direction is greatly
> > appreciated.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Memcache issues 3/14

[Ikai Lan (Google)]

Okay. I'm going to leave this issue alone for the time being as it seems to
have been transient, possibly a symptom of some of the other things going
on/ongoing production work (but I shouldn't speculate). There are other,
more pressing issues globally at the moment.


--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 5:35 PM, Sekhar Ravinutala wrote:

> Well, I expect not to get errors, of course. I'm putting entity (JPA)
> instances on the cache. I see a whole bunch of memcache errors (read as
> well as write on multiple entities) on the log between 8:06am and 8:12am
> today, and no errors since. Thanks,
>
> -Sekhar
>
>
> On Wed, Mar 14, 2012 at 1:31 PM, Ikai Lan (Google) wrote:
>
>> What do you expect to happen? What are you putting? What percentage of
>> errors are you seeing? Is this still happening?
>>
>> --
>> Ikai Lan
>> Developer Programs Engineer, Google App Engine
>> plus.ikailan.com
>>
>>
>>
>> On Wed, Mar 14, 2012 at 1:10 PM, Sekhar  wrote:
>>
>>> Sure, thanks for responding.
>>>
>>> Our app is wellaho-sanitas. Below are few of the many error traces we
>>> saw this morning, hope these will help pin down the issue. I'll be happy to
>>> give additional details.
>>>
>>>
>>>1. 2012-03-14 08:11:18.736 /gwtRequest 200 6058ms 0kb Mozilla/5.0
>>>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>>>Chrome/18.0.1025.56 Safari/535.19
>>>
>>>99.52.100.16 - allurefx [14/Mar/2012:08:11:18 -0700] "POST /gwtRequest 
>>> HTTP/1.1" 200 181 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
>>> (KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
>>> "wellaho-sanitas.appspot.com" ms=6058 cpu_ms=661 api_cpu_ms=505 
>>> cpm_usd=0.018529 instance=00c61b117c351882ddb272a307017ebc39ec 
>>> 
>>>
>>>2. W2012-03-14 08:11:17.842
>>>
>>>com.sanitas.wellaho.server.Wellaho printStackTrace: 
>>> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
>>> Error setting single item (Quote9001)
>>> at 
>>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>>> at 
>>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>>> at 
>>> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>>> at 
>>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>>> at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
>>> Source)
>>>
>>>
>>>
>>>
>>>
>>>2012-03-14 08:10:46.272
>>>
>>>
>>>com.sanitas.wellaho.server.Wellaho printStackTrace: 
>>> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
>>> Error setting single item 
>>> (ProblemahFzfndlbGxhaG8tc2FuaXRhc3IeCxIEVXNlciIGbmFzZXJwDAsSB1Byb2JsZW0YtkYM)
>>> at 
>>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>>> at 
>>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>>> at 
>>> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>>> at 
>>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>>> at 
>>> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>>> at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
>>> Source)
>>>
>>>
>>>
>>>1. 2012-03-14 08:10:36.955 /gwtRequest 200 10024ms 0kb Mozilla/5.0
>>>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>>>Chrome/18.0.1025.56 Safari/535.19
>>>
>>>99.52.100.16 - allurefx [14/Mar/2012:08:10:36 -0700] "POST /gwtRe

Re: [google-appengine] Re: Memcache issues 3/14

[Sekhar Ravinutala]

Well, I expect not to get errors, of course. I'm putting entity (JPA)
instances on the cache. I see a whole bunch of memcache errors (read as
well as write on multiple entities) on the log between 8:06am and 8:12am
today, and no errors since. Thanks,

-Sekhar


On Wed, Mar 14, 2012 at 1:31 PM, Ikai Lan (Google) wrote:

> What do you expect to happen? What are you putting? What percentage of
> errors are you seeing? Is this still happening?
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Wed, Mar 14, 2012 at 1:10 PM, Sekhar  wrote:
>
>> Sure, thanks for responding.
>>
>> Our app is wellaho-sanitas. Below are few of the many error traces we saw
>> this morning, hope these will help pin down the issue. I'll be happy to
>> give additional details.
>>
>>
>>1. 2012-03-14 08:11:18.736 /gwtRequest 200 6058ms 0kb Mozilla/5.0
>>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>>Chrome/18.0.1025.56 Safari/535.19
>>
>>99.52.100.16 - allurefx [14/Mar/2012:08:11:18 -0700] "POST /gwtRequest 
>> HTTP/1.1" 200 181 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
>> (KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
>> "wellaho-sanitas.appspot.com" ms=6058 cpu_ms=661 api_cpu_ms=505 
>> cpm_usd=0.018529 instance=00c61b117c351882ddb272a307017ebc39ec 
>> 
>>
>>2. W2012-03-14 08:11:17.842
>>
>>com.sanitas.wellaho.server.Wellaho printStackTrace: 
>> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
>> Error setting single item (Quote9001)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>>  at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
>> Source)
>>
>>
>>
>>2012-03-14 08:10:46.272
>>
>>com.sanitas.wellaho.server.Wellaho printStackTrace: 
>> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
>> Error setting single item 
>> (ProblemahFzfndlbGxhaG8tc2FuaXRhc3IeCxIEVXNlciIGbmFzZXJwDAsSB1Byb2JsZW0YtkYM)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>>  at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
>> Source)
>>
>>
>>
>>1. 2012-03-14 08:10:36.955 /gwtRequest 200 10024ms 0kb Mozilla/5.0
>>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>>Chrome/18.0.1025.56 Safari/535.19
>>
>>99.52.100.16 - allurefx [14/Mar/2012:08:10:36 -0700] "POST /gwtRequest 
>> HTTP/1.1" 200 197 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
>> (KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
>> "wellaho-sanitas.appspot.com" ms=10025 cpu_ms=218 api_cpu_ms=8 
>> cpm_usd=0.006296 instance=00c61b117c351882ddb272a307017ebc39ec 
>> 
>>
>>2. W2012-03-14 08:10:36.884
>>
>>com

[google-appengine] Does the python dev server have this flag: Ddatastore.default_high_rep_job_policy_unapplied_job_pct? Java does

[Kurt]

Hi,

I'm testing my HR migration and I'm using the --high_replication flag on 
the dev server.  It seems to be saving data too fast - I cannot get 
inconsistent results on subsequent responses (despite querying across 
entity groups).

I notice the java server has: 
Ddatastore.default_high_rep_job_policy_unapplied_job_pct, 
which can be used to tune it up and down.

Does the python server have something similar?

Please help me break my app, so I know my Entity Group fixes will work :)

Thanks,
Kurt

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/tgzyv9Cw2ecJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Datastore offline as of 3:40pm PST

[blackpawn]

Thanks for keeping us up to date Ikai!

On Wednesday, March 14, 2012 12:37:00 PM UTC-7, Ikai Lan wrote:
>
> I've updated the status page for the network disruption yesterday:
>
> http://code.google.com/status/appengine
>
> Dishonesty is not the intention. There's been talk about rebuilding the 
> status site from scratch because a lot of the reporting could use 
> improvement - there's a view some team members share that an incorrect 
> status site is worse than no status site. 
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Mon, Mar 12, 2012 at 11:27 PM, devlike wrote:
>
>> 3 days later, the service status page shows all green for the past week.  
>> Seems a bit less than honest.
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/google-appengine/-/pWUz1T_OFAUJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/0-37PtpDscUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore offline as of 3:40pm PST

[John]

On Friday, March 9, 2012 4:17:01 PM UTC-8, blackpawn wrote:
>
> It seemed like a complete failure.  My app does use the capabilities API 
> and handles read only properly but no non-static requests succeeded.  Even 
> requests that only wind up hitting memcache were failing too actually.  The 
> errors were all "A problem was encountered with the process that handled 
> this request, causing it to exit." and "Request was aborted after waiting 
> too long to attempt to service your request."
>

Thanks for satisfying my curiosity! Sounds like your code didn't fare any 
better than ours in this outage.


> On Friday, March 9, 2012 4:10:53 PM UTC-8, John wrote:
>>
>> It's recommended that we make use of the CapabilitiesService. This lets 
>> you get values like "UNKNOWN" and "DISABLED" for things like 
>> "DATASTORE_WRITE". I'm curious what value it would have provided during 
>> this period.
>>
>> On Friday, March 9, 2012 3:59:36 PM UTC-8, blackpawn wrote:
>>>
>>> The datastore is completely dead since 3:40 and non-HRD apps can't serve 
>>> any requests besides static files.  The status page is showing Anomaly so 
>>> hopefully this is being looked at.  Is there anything we can do to prevent 
>>> our apps from going nuts during this period spawning tons of instances that 
>>> just time out but still charge us money for CPU?
>>
>>
On Friday, March 9, 2012 4:17:01 PM UTC-8, blackpawn wrote:
>
> It seemed like a complete failure.  My app does use the capabilities API 
> and handles read only properly but no non-static requests succeeded.  Even 
> requests that only wind up hitting memcache were failing too actually.  The 
> errors were all "A problem was encountered with the process that handled 
> this request, causing it to exit." and "Request was aborted after waiting 
> too long to attempt to service your request."
>
> On Friday, March 9, 2012 4:10:53 PM UTC-8, John wrote:
>>
>> It's recommended that we make use of the CapabilitiesService. This lets 
>> you get values like "UNKNOWN" and "DISABLED" for things like 
>> "DATASTORE_WRITE". I'm curious what value it would have provided during 
>> this period.
>>
>> On Friday, March 9, 2012 3:59:36 PM UTC-8, blackpawn wrote:
>>>
>>> The datastore is completely dead since 3:40 and non-HRD apps can't serve 
>>> any requests besides static files.  The status page is showing Anomaly so 
>>> hopefully this is being looked at.  Is there anything we can do to prevent 
>>> our apps from going nuts during this period spawning tons of instances that 
>>> just time out but still charge us money for CPU?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/o_dvOmkXJW8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Admin email size limit?

[Mars]

Is there a size limit for sending email to admins using
mail.send_mail_to_admins()? I'm getting the following exception:

  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/mail.py", line 418, in send_mail_to_admins
message.send(make_sync_call)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/mail.py", line 897, in send
raise ERROR_MAP[e.application_error](e.error_detail)
  BadRequestError: Admin message exceeds size limits

The same email body sends without any issue using mail.send_mail()

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] serving images stored in the cloud storage as files

[hugues2]

Hi,

Just one quick question, what is the url to used in the internet browser to 
display images that have been stored in the Google cloud storage through 
Google App Engine ? Also, what prevents other people to be granted access 
to these images if they have the access url ?

Thanks a lot for your help !

Cheers,

Hugues

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/1kSfLKpkZzcJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Ikai Lan (Google)]

Mos,

There have been several responses posted to various threads. I'll go back
to those threads and update if there is new information. The disruption to
HRD has been posted to the System Status site, and a new maintenance period
has been announced on Monday to deal with Master/Slave serving issues (
https://groups.google.com/forum/?fromgroups#!forum/google-appengine-downtime-notify
).

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 11:58 AM, alex  wrote:

> What Brandon is trying to say here, I think, is that SLA covers only paid
> apps.
>
>
> On Wednesday, March 14, 2012 6:39:41 PM UTC+1, Brandon Wirtz wrote:
>>
>> Non-payed apps have rules all of their own, they get slow sometimes for
>> no reason. I would not say this is an issue, it just is you are in the
>> lowest tier so if you get squished no one cares….
>>
>>
>>
>> I think QoS/QoE is set this way on purpose.
>>
>>
>>
>> *From:* 
>> google-appengine@googlegroups.**com[mailto:
>> google-appengine@**googlegroups.com ]
>> *On Behalf Of *Mos
>> *Sent:* Wednesday, March 14, 2012 10:16 AM
>> *To:* google-appengine@googlegroups.**com
>> *Subject:* Re: [google-appengine] More then 100 complains and no
>> feedback from Google. Was: Outages?
>>
>>
>>
>> Hi Alex,
>>
>> right, 1 instance is billed, cause this application runs in non payed
>> mode, but the scheduler spans up to four instances (without real need).
>> In payed mode I assume the green line would not be on 1 instance all the
>> time...  (I'm glad I didn't activate payment yet)
>>
>> Graphs are attached.
>>
>> According to Google Analytic and application logging there was similar
>> usages then the days before.  (Around one to two request the minute)
>> I think we don't need to discuss that something bad is going on the last
>> 24h to 48h hours for many GAE users?
>> Please check issue tickets and other postings here.
>>
>>
>>
>>
>>
>>
>> On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:
>>
>> Funny... maybe I'm not getting something here but, where's the issue? It
>> is crystal clear from your graphs that you are being billed for 1 instance
>> only, all the times.
>>
>>
>>
>> Can you show CPU ms used/sec and Errors/sec graphs?
>>
>>
>>
>> On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:
>>
>> And here are two that are related to this thread  (application has same
>> traffic, load and configuration for days  --> major GAE problem for more
>> then 24 hours):
>>
>> Attached
>>
>>
>>
>>
>>
>> On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz 
>> wrote:
>>
>> Nah it is all shiny… And that couple of hours when there are no logs,
>> that was just cause everyone was sleeping…
>>
>> This is just a pretty picture… It’s not related to this thread. J
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to 
>> google-appengine@googlegroups.**com
>> .
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscribe@**googlegroups.com
>> .
>> For more options, visit this group at http://groups.google.com/**
>> group/google-appengine?hl=en
>> .
>>
>>
>>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>>
>> To view this discussion on the web visit https://groups.google.com/d/**
>> msg/google-appengine/-/tk8Xo_**fvQ04J
>> .
>>
>>
>> To post to this group, send email to 
>> google-appengine@googlegroups.**com
>> .
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscribe@**googlegroups.com
>> .
>> For more options, visit this group at http://groups.google.com/**
>> group/google-appengine?hl=en
>> .
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to 
>> google-appengine@googlegroups.**com
>> .
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscribe@**googlegroups.com
>> .
>> For more options, visit this group at http://groups.google.com/**
>> group/google-appengine?hl=en
>> .
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/xE-3gLJqg-cJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post 

Re: [google-appengine] Re: Memcache issues 3/14

[Ikai Lan (Google)]

What do you expect to happen? What are you putting? What percentage of
errors are you seeing? Is this still happening?

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 1:10 PM, Sekhar  wrote:

> Sure, thanks for responding.
>
> Our app is wellaho-sanitas. Below are few of the many error traces we saw
> this morning, hope these will help pin down the issue. I'll be happy to
> give additional details.
>
>
>1. 2012-03-14 08:11:18.736 /gwtRequest 200 6058ms 0kb Mozilla/5.0
>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>Chrome/18.0.1025.56 Safari/535.19
>
>99.52.100.16 - allurefx [14/Mar/2012:08:11:18 -0700] "POST /gwtRequest 
> HTTP/1.1" 200 181 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
> (KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
> "wellaho-sanitas.appspot.com" ms=6058 cpu_ms=661 api_cpu_ms=505 
> cpm_usd=0.018529 instance=00c61b117c351882ddb272a307017ebc39ec 
> 
>
>2. W2012-03-14 08:11:17.842
>
>com.sanitas.wellaho.server.Wellaho printStackTrace: 
> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
> Error setting single item (Quote9001)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>   at 
> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>   at 
> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>   at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
> Source)
>
>
>2012-03-14 08:10:46.272
>
>
>com.sanitas.wellaho.server.Wellaho printStackTrace: 
> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
> Error setting single item 
> (ProblemahFzfndlbGxhaG8tc2FuaXRhc3IeCxIEVXNlciIGbmFzZXJwDAsSB1Byb2JsZW0YtkYM)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>   at 
> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>   at 
> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>   at 
> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
>   at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
> Source)
>
>
>
>1. 2012-03-14 08:10:36.955 /gwtRequest 200 10024ms 0kb Mozilla/5.0
>(Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko)
>Chrome/18.0.1025.56 Safari/535.19
>
>99.52.100.16 - allurefx [14/Mar/2012:08:10:36 -0700] "POST /gwtRequest 
> HTTP/1.1" 200 197 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
> (KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
> "wellaho-sanitas.appspot.com" ms=10025 cpu_ms=218 api_cpu_ms=8 
> cpm_usd=0.006296 instance=00c61b117c351882ddb272a307017ebc39ec 
> 
>
>2. W2012-03-14 08:10:36.884
>
>com.sanitas.wellaho.server.Wellaho printStackTrace: 
> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
> Error setting single item (Statesekhar&133153560)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>   at 
> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceI

Re: [google-appengine] Do maintentance periods really have to be during core working hours?

[Ikai Lan (Google)]

Our next maintenance period is from 6-8pm, but that's a coincidence more
than any other reason.

First off, we really want to encourage you to migrate to High Replication.
I can't stress this enough. This allows us to do lots of work to App Engine
without impacting your application's service. I know some people have been
holding off because the blobstore migration tool doesn't exist yet; this is
coming.

One of the reasons we like having maintenances at certain times is because
of one of App Engine's strengths: it's built using a lot of Google's
existing infrastructure (the datastore uses Megastore, which uses BigTable,
for instance). By performing maintenance during US/Pacific working hours
(or close), we can always ensure that if we need to contact another team,
that we can minimize the delay of finding someone at home.

We love High Replication because it lets us hide away all of the work that
needs to happen to keep a system as large as App Engine online. Please
embrace it!

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 1:08 PM, Per  wrote:

> Although I'm overall happy with GAE, and I know that the maintenance
> periods "only" affect M/S. And I don't mind the occasional one either. But
> I find it increasingly frustrating that they always have to be scheduled in
> the middle of the week, and during a time that most of our US clients would
> still call core working hours.
>
> I am now pasting the third downtime notice in a month onto our
> application's dashboard. Yeah I know that one maintenance period didn't
> actually happen, but it was cancelled too late, all our clients had already
> gotten our downtime warning, which is almost as bad.
>
> I am wondering why these maintenance periods cannot be done on the
> weekend, or at least later during the day? How about 6pm to 8pm PST for
> instance? That's still late at night in Europe, it's just about as annoying
> for APAC, but at least it's a lot better for US users. And it's not *that*
> late so that East Coast Googlers have to get up in the dead of the night
> either.
>
> Or am mistaken and the typical usage pattern is "after hours", because
> nobody except for us dared to use GAE for an enterprise application? :)
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/bK7kFbD_8E4J.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Memcache issues 3/14

[Sekhar]

Sure, thanks for responding.

Our app is wellaho-sanitas. Below are few of the many error traces we saw 
this morning, hope these will help pin down the issue. I'll be happy to 
give additional details.


   1. 2012-03-14 08:11:18.736 /gwtRequest 200 6058ms 0kb Mozilla/5.0 
   (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) 
   Chrome/18.0.1025.56 Safari/535.19
   
   99.52.100.16 - allurefx [14/Mar/2012:08:11:18 -0700] "POST /gwtRequest 
HTTP/1.1" 200 181 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
(KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
"wellaho-sanitas.appspot.com" ms=6058 cpu_ms=661 api_cpu_ms=505 
cpm_usd=0.018529 instance=00c61b117c351882ddb272a307017ebc39ec 

   
   2. W2012-03-14 08:11:17.842
   
   com.sanitas.wellaho.server.Wellaho printStackTrace: 
com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: Error 
setting single item (Quote9001)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
at 
com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
at 
com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
at 
com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
Source)
   
   
   2012-03-14 08:10:46.272
   
   com.sanitas.wellaho.server.Wellaho printStackTrace: 
com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: Error 
setting single item 
(ProblemahFzfndlbGxhaG8tc2FuaXRhc3IeCxIEVXNlciIGbmFzZXJwDAsSB1Byb2JsZW0YtkYM)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
at 
com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
at 
com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
at 
com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:71)
at com.google.appengine.api.memcache.jsr107cache.GCache.put(Unknown 
Source)
   
   

   1. 2012-03-14 08:10:36.955 /gwtRequest 200 10024ms 0kb Mozilla/5.0 
   (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) 
   Chrome/18.0.1025.56 Safari/535.19
   
   99.52.100.16 - allurefx [14/Mar/2012:08:10:36 -0700] "POST /gwtRequest 
HTTP/1.1" 200 197 - "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 
(KHTML, like Gecko) Chrome/18.0.1025.56 Safari/535.19" 
"wellaho-sanitas.appspot.com" ms=10025 cpu_ms=218 api_cpu_ms=8 cpm_usd=0.006296 
instance=00c61b117c351882ddb272a307017ebc39ec 

   
   2. W2012-03-14 08:10:36.884
   
   com.sanitas.wellaho.server.Wellaho printStackTrace: 
com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: Error 
setting single item (Statesekhar&133153560)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
at 
com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
at 
com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.

[google-appengine] Do maintentance periods really have to be during core working hours?

[Per]

Although I'm overall happy with GAE, and I know that the maintenance 
periods "only" affect M/S. And I don't mind the occasional one either. But 
I find it increasingly frustrating that they always have to be scheduled in 
the middle of the week, and during a time that most of our US clients would 
still call core working hours. 

I am now pasting the third downtime notice in a month onto our 
application's dashboard. Yeah I know that one maintenance period didn't 
actually happen, but it was cancelled too late, all our clients had already 
gotten our downtime warning, which is almost as bad.

I am wondering why these maintenance periods cannot be done on the weekend, 
or at least later during the day? How about 6pm to 8pm PST for instance? 
That's still late at night in Europe, it's just about as annoying for APAC, 
but at least it's a lot better for US users. And it's not *that* late so 
that East Coast Googlers have to get up in the dead of the night either.

Or am mistaken and the typical usage pattern is "after hours", because 
nobody except for us dared to use GAE for an enterprise application? :)

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/bK7kFbD_8E4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Is it possible to query Datastore by parameter of Date?

[Ikai Lan (Google)]

Tony,

Try asking this question on StackOverflow with the google-app-engine tag:

https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Sun, Mar 11, 2012 at 6:50 PM, Tony Yang  wrote:

> Dear Sir,
> Would you help the issue below. Is it possible to query Datastore by
> parameter of Date?
>
> --- My code 
> PersistenceManager pm = PMF.get().getPersistenceManager();
> Query query = pm.newQuery(Customer.class);
> Date currentDate = new Date();
> Date beforeDate = new Date();
> long currentdate = currentDate.getTime();
> long beforedate = currentdate - 8640*5; //search data in
> Customer.class within 5 days
> beforeDate.setTime(beforedate);
> query.setFilter("date > offsetDate"); // date is
> column's name in Customer.class
> query.declareParameters("Date offsetDate");
> List conn = (List)
> pm.newQuery(query).execute(beforeDate);
>
> --- Error message from system is as below :
>
>Class Date for query has not been resolved. Check the query and
> any imports specification
>
> Thanks a lot.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Channel API not working in production

[Ikai Lan (Google)]

Praveen,

Try asking this question on StackOverflow:

https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w

Also, it would be helpful to provide more details when you do. "It sucks"
is terrible information. That kind of feedback is not actionable.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Mon, Mar 12, 2012 at 3:58 AM, praveen wrote:

> I have implement struts based chat application using channel API
> trying to implement the chat application., The Sample struts chat
> application works in local enviroinment .But in production
> enviroinment totally it sucks.Please help
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] using GAE with javascript

[Ikai Lan (Google)]

I wouldn't say dancing - we just don't provide that kind of access. Even if
we ever did in the future, we would likely wrap an auth layer around it
(probably OAuth 2.0).

This might be the closest thing you are looking for:

http://code.google.com/p/google-protorpc/

But I don't have any thoughts about security, and you'd have to write the
code yourself to translate requests to datastore calls.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Mon, Mar 12, 2012 at 8:31 PM, that an  wrote:

> I'm looking for a way to use javascript code to directly interface
> with the google app engine and with the datastore.
>
> I've already used the GWT/GAE Java SDK in Eclipse with varying levels
> of success, but I'm looking for a way to leverage the benefits of GAE
> cloud services with the direct DOM manipulation of writing javascript
> directly for the client.  GWT front end just doesn't seem flexible
> enough to do what javascript can.
>
> Maybe I've missed something obvious, or something that is out there
> does it, but I've been searching for awhile now, and it just seems
> like Google is dancing around any direct client access to their App
> Engine and cloud datastore.
>
> I've pretty much exhausted my leads so far - Any direction is greatly
> appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Java Error code 104: A problem was encountered with the process that handled this request, causing it to exit

[Ikai Lan (Google)]

Matt,

There was definitely an issue with Java HRD when you posted this. We've
been addressing these issues. Are you still seeing issues?

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Mon, Mar 12, 2012 at 3:43 PM, Matt Mastracci  wrote:

> Hey all,
>
> Has anyone been seeing a large number of error code 104s today? We haven't
> made any significant code changes today, but these started showing up in
> logs, with no additional information.
>
> I've tried upgrading our instance types to F2, just in case we're hitting
> some sort of memory limit, but it doesn't appear to have helped. I've
> noticed that there's a Java issue on the status screen: could this be
> related?
>
> Attached is a graph showing the milliseconds/request graph, which seems to
> correlate with the issue we've been seeing.
>
>
>1.
>   1.
>
>   A problem was encountered with the process that handled this request, 
> causing it to exit. This is likely to cause a new process to be used for the 
> next request to your application. If you see this message frequently, you may 
> be throwing exceptions during the initialization of your application. (Error 
> code 104)
>
>   2.
>   1.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/T12g_EHTjigJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Datastore offline as of 3:40pm PST

[Ikai Lan (Google)]

I've updated the status page for the network disruption yesterday:

http://code.google.com/status/appengine

Dishonesty is not the intention. There's been talk about rebuilding the
status site from scratch because a lot of the reporting could use
improvement - there's a view some team members share that an incorrect
status site is worse than no status site.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Mon, Mar 12, 2012 at 11:27 PM, devlike wrote:

> 3 days later, the service status page shows all green for the past week.
> Seems a bit less than honest.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/pWUz1T_OFAUJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Design problem - How to avoid datastore contention

[Ikai Lan (Google)]

Looks like it was answered, and pretty well, too.

In general, it's not really necessary to post both to StackOverflow and
groups.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 3:48 AM, Sahid Orentino Ferdjaoui <
sahid.ferdja...@gmail.com> wrote:

> Hi all
>
> I have a question on stackoverflow about avoiding datastore contention, if
> anybody can help me.
>
> http://stackoverflow.com/questions/9700388/avoiding-datastore-contention
>
> Thanks a lot!
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/-kEBUznzgxsJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Felippe Bueno]

Hello all. Only to share my information:

My app is doing something like this:

JS="xpto"
JS_OPTOUT="xpto1"

if request.cookie.has_key("optout") or request.headers.has_key("DNT")
 response.write(JS_OPTOUT)
else
 response.write(JS)


The normal latency is ~3ms
Now I'm seeing 13.9 ms

Earlier this morning I saw ~1000ms milisec/req
24hours ago I saw ~2400ms milisec/req

[image: Requests/Second (24 hrs)]

I noticed this behavior on all my apps for at least the last 8 days.


I'm using python 2.5/HRD.



On Wed, Mar 14, 2012 at 5:35 AM, Nicanor Babula wrote:

> Now my app is working fine. What happened? I saw at some point my app's
> graphs reset and some huge values for instance hours values. Afterwards,
> the instance hours counters turned to normal and my app stpped raising
> errors. If there was the GAE team working on it, thank you very much, but I
> think you owe us at least an explanation. What should I say to my
> customers? The issue has been fixed or they should  be expecting outages in
> the following days? My app is on HRD.
>
> Thanks,
> Cristian
>
>
> Il giorno martedì 6 marzo 2012 22:17:37 UTC+1, Adam Sherman ha scritto:
>
>> Am I the only one seeing short duration outages? They are being reflected
>> at:
>>
>> http://code.google.com/status/**appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/hw3niAzjSIAJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Very high latency since March 13th

[Ikai Lan (Google)]

We're addressing issues with high replication datastore applications.

In the future, however, this information is typically not enough. What are
you doing? Are you making datastore calls? Are you doing URLFetch? Are you
making XMPP or email API calls? Are CPU intensive tasks slower? This is
important because there are a lot of operations for which 200ms would seem
low latency. If you're trying to brute force SHA1 hashes and it's taking
500ms on average, you're doing okay.

One of the fortunate things about working with software developers instead
of normal internet consumers is that I can usually just give the guidance,
"report issues that way you want your users to report issues or bugs", and
it gets the message across =).

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 5:48 AM, andidol  wrote:

> Hi,
>
> I have very high latency on my AppEngine since yesterday. It was really
> fast before < 100ms. Now there are a lot of requests performing with >
> 200ms without any reason. I did not update or did anything.
> I'm using High Replication Datastore.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/UKDaOm5bNJsJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: High Replication latencies and it's related costs.

[thecheatah]

The over all requests/second have been consistent from day to day. I
am talking about the ability of a single machine's ability to handle
requests/second.

Ravneet

On Mar 14, 12:19 am, Gopal Patel  wrote:
> if request/second dropped, nothing could be done. latency has nothing to do
> with request/second. if nothing else, it will increase the instance count,
> google have no control over request/second.
>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 9:47 AM, thecheatah  wrote:
> > Hi,
>
> > I am noticing that the latency on my HR based application went up
> > significantly. My app does a simple read and a write. It is taking
> > over 1 second to do this operation. In M/S the this operation was <
> > 100ms
>
> > Even under multi threading, my machines are not processing as many
> > requests as my M/S app could handle. My costs have gone up by 50%
> > after having switched from M/S. Is this normal?
>
> > Last night a single machine handled about 6-7 requests/second. Today
> > it has dropped to 4. Nothing has changed. The request are generated by
> > devices and thus are very consistent.
>
> > It seems that the latency on the HR datastore is causing my cost to
> > increase. I have no control over this latency. Is this something I can
> > get money back for?
>
> > Ravneet
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] High Replication latencies and it's related costs.

[Ikai Lan (Google)]

Can you post the code about what you are doing? "Simple read and write"
isn't descriptive enough.

There have been issues with High Replication, but these are/have been
addressed.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Tue, Mar 13, 2012 at 9:17 PM, thecheatah  wrote:

> Hi,
>
> I am noticing that the latency on my HR based application went up
> significantly. My app does a simple read and a write. It is taking
> over 1 second to do this operation. In M/S the this operation was <
> 100ms
>
> Even under multi threading, my machines are not processing as many
> requests as my M/S app could handle. My costs have gone up by 50%
> after having switched from M/S. Is this normal?
>
> Last night a single machine handled about 6-7 requests/second. Today
> it has dropped to 4. Nothing has changed. The request are generated by
> devices and thus are very consistent.
>
> It seems that the latency on the HR datastore is causing my cost to
> increase. I have no control over this latency. Is this something I can
> get money back for?
>
> Ravneet
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[alex]

What Brandon is trying to say here, I think, is that SLA covers only paid 
apps.


On Wednesday, March 14, 2012 6:39:41 PM UTC+1, Brandon Wirtz wrote:
>
> Non-payed apps have rules all of their own, they get slow sometimes for no 
> reason. I would not say this is an issue, it just is you are in the lowest 
> tier so if you get squished no one cares….
>
>  
>
> I think QoS/QoE is set this way on purpose.
>
>  
>
> *From:* google-appengine@googlegroups.com [mailto:
> google-appengine@googlegroups.com] *On Behalf Of *Mos
> *Sent:* Wednesday, March 14, 2012 10:16 AM
> *To:* google-appengine@googlegroups.com
> *Subject:* Re: [google-appengine] More then 100 complains and no feedback 
> from Google. Was: Outages?
>
>  
>
> Hi Alex,
>
> right, 1 instance is billed, cause this application runs in non payed 
> mode, but the scheduler spans up to four instances (without real need).
> In payed mode I assume the green line would not be on 1 instance all the 
> time...  (I'm glad I didn't activate payment yet)
>
> Graphs are attached.
>
> According to Google Analytic and application logging there was similar 
> usages then the days before.  (Around one to two request the minute)
> I think we don't need to discuss that something bad is going on the last 
> 24h to 48h hours for many GAE users?
> Please check issue tickets and other postings here.
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:
>
> Funny... maybe I'm not getting something here but, where's the issue? It 
> is crystal clear from your graphs that you are being billed for 1 instance 
> only, all the times.
>
>  
>
> Can you show CPU ms used/sec and Errors/sec graphs?
>
>
>
> On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:
>
> And here are two that are related to this thread  (application has same 
> traffic, load and configuration for days  --> major GAE problem for more 
> then 24 hours):
>
> Attached
>
>
>
>
>
> On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz  
> wrote:
>
> Nah it is all shiny… And that couple of hours when there are no logs, that 
> was just cause everyone was sleeping… 
>
> This is just a pretty picture… It’s not related to this thread. J
>
>  
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>  
>
>  
>
>  
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-appengine/-/tk8Xo_fvQ04J.
>
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>  
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/xE-3gLJqg-cJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Ikai Lan (Google)]

We've been working on addressing the issues with HRD apps.  Your experience
is probably a coincidence.

There is a very small section of apps that will have a few requests (very
small %) that will be a LOT slower.

We've scheduled a maintenance period for March 19th that will attempt to
address issues with master/slave. You can read more about it here (scroll
to the bottom for the correct time):

https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/CO_x02OF9Ak

In general, everyone should try to migrate your application to High
Replication when they can because we have a much higher speed of iteration
when implementing different fixes for production issues (I have an earlier
post about why this matters - we can make almost any production changes we
want to HR apps without causing app downtime). At this point, I would not
even create development or staging applications using master/slave because
some behaviors (eventually consistency on global queries without an entity
group root) differ between master/slave and high replication.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 1:35 AM, Nicanor Babula wrote:

> Now my app is working fine. What happened? I saw at some point my app's
> graphs reset and some huge values for instance hours values. Afterwards,
> the instance hours counters turned to normal and my app stpped raising
> errors. If there was the GAE team working on it, thank you very much, but I
> think you owe us at least an explanation. What should I say to my
> customers? The issue has been fixed or they should  be expecting outages in
> the following days? My app is on HRD.
>
> Thanks,
> Cristian
>
>
> Il giorno martedì 6 marzo 2012 22:17:37 UTC+1, Adam Sherman ha scritto:
>
>> Am I the only one seeing short duration outages? They are being reflected
>> at:
>>
>> http://code.google.com/status/**appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/hw3niAzjSIAJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: How to secure the SDK

[Ikai Lan (Google)]

This is a great question for StackOverflow because you'll get a lot more
responses if you tag it correctly.

On Linux you have a lot of options. One of the easiest ones is iptables.
Well ... "easiest".

PERSONAL OPINION ALERT: I highly recommend learning Linux or working with a
*nix system. I find that it's way easier to do software development on that
kind of a system than trying to deal with Windows. Not to mention: I've
rarely been in a situation using Linux where I've wanted to do some weird
networking or security thing and not been able to find at least a
half-assed guide somewhere describing how to do it (and, in struggling with
said half-assed guide, become slightly better at using Linux myself). IMO
there really aren't any good reasons why you can't learn Linux. If you
don't want to dual boot, you can always use a tool like VirtualBox and run
an Ubuntu ISO. There's no dollar cost.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 4:01 AM, Kaan Soral  wrote:

> Great idea
>
> What would be an easy solution to permit access for only a range of IP's?
> Preferrably with logging etc to deny first and allow later.
> On windows and for a network noob - This is probably not the right place
> for asking this but it would be great if any of you have suggestions
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/IGQV9BWzPEsJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] SITE SLOW AND DOWN

[Ikai Lan (Google)]

Tony,

A stack trace is usually not enough information. I've seen you post in
another thread. Can you follow those steps?

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 8:45 AM, agp  wrote:

> I am getting a ton of issues like this today making the site basicly
> down because they get a error page  with a stack trace (pasted below):
>
> 2012-03-14 10:41:34.194 [s~madisonpsa/8.356247106902853044].:
> [ERROR] CacheServiceImpl - -Memcache put: Error setting single item
> (org.vosao.entity.LanguageEntitygetB
> W 2012-03-14 10:41:52.539 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (entity:org.vosao.entity.TemplateEnt
> W 2012-03-14 10:41:57.460 [s~madisonpsa/
> 8.356247106902853044].: [INFO] PluginClassLoader - -creating
> class loader sitemap
> W 2012-03-14 10:42:01.778 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Set failed to set 1 keys: entity:org.vosao.entity.PluginResour
> W 2012-03-14 10:42:02.783 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (sitemappluginResourceList)
> W 2012-03-14 10:42:05.278 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Set failed to set 1 keys: entity:org.vosao.entity.PluginResour
> W 2012-03-14 10:42:07.145 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (org.vosao.plugins.sitemap.SitemapVe
> W 2012-03-14 10:42:09.108 [s~madisonpsa/
> 8.356247106902853044].: [INFO] PluginClassLoader - -creating
> class loader superfish
> W 2012-03-14 10:42:12.892 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (org.vosao.entity.PluginResourceEnti
> W 2012-03-14 10:42:14.646 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl -
> -Memcache put: Error setting single item (superfishpluginResourceList)
> W 2012-03-14 10:42:15.650 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (org.vosao.plugins.superfish.Superfi
> W 2012-03-14 10:42:20.731 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (superfishpluginResourceList)
> W 2012-03-14 10:42:21.734 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
> put: Error setting single item (org.vosao.plugins.superfish.Superfi
> W 2012-03-14 10:42:24.521 [s~madisonpsa/
> 8.356247106902853044].: [ERROR] QueryCacheImpl - -
> com.google.apphosting.api.DeadlineExceededException: This request
> (2b3888250c4
> W 2012-03-14 10:42:24.522 [s~madisonpsa/
> 8.356247106902853044].:
> W 2012-03-14 10:42:25.113 Error for /
> com.google.apphosting.runtime.HardDeadlineExceededError: This request
> (2b3888250c44649b) started at 2012/03/14 15:41:24.773 UTC and was st
> C 2012-03-14 10:42:25.120 Uncaught exception from servlet
> com.google.apphosting.runtime.HardDeadlineExceededError: This request
> (2b3888250c44649b) started at 2012/03/14 15:41:2
> I 2012-03-14 10:42:25.124 This request caused a new process to be
> started for your application, and thus caused your application code to
> be loaded for the first time. This requ
> W 2012-03-14 10:42:25.124 A problem was encountered with the process
> that handled this request, causing it to exit. This is likely to cause
> a new process to be used for the nex
>
>
>
> Error Page:
> Uncaught exception from servlet
> com.google.apphosting.api.ApiProxy$CancelledException: The API call
> datastore_v3.Put() was explicitly cancelled.
>at
> com.google.apphosting.runtime.ApiProxyImpl$5.get(ApiProxyImpl.java:
> 359)
>at
> com.google.apphosting.runtime.ApiProxyImpl$5.get(ApiProxyImpl.java:
> 357)
>at
> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:
> 90)
>at com.google.appengine.api.datastore.FutureHelper
> $CumulativeAggregateFuture.get(FutureHelper.java:145)
>at
> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:
> 90)
>at
>
> com.google.appengine.api.datastore.FutureHelper.getInternal(FutureHelper.java:
> 72)
>at
> com.google.appengine.api.datastore.FutureHelper.quietGet(FutureHelper.java:
> 33)
>at com.google.appengine.api.datastore.DatastoreServiceImpl
> $2.runInternal(DatastoreServiceImpl.java:113)
>at com.google.appengine.api.datastore.DatastoreServiceImpl
> $2.runInternal(DatastoreServiceImpl.java:110)
>at
>
> com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:
> 31)
>at
>
> com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:
> 110)
>at
>
> com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:
> 94)
>at
>
> com.google.apphosting.runtime.je

Re: [google-appengine] Re: Memcache issues 3/14

[Ikai Lan (Google)]

Can you describe the issues and post an app ID? Ex:

Expected: Memcache performs with under a 0.1% error rate typically on GET
Observed: Memcache times out after 5 seconds on 10% of GETs

If there are specific reproduction steps, those are very useful too (we're
all software engineers too, so it helps when you yourself try to model
issue reports after well written bugs you've read).

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Wed, Mar 14, 2012 at 8:46 AM, agp  wrote:

> I am too, I just put a different post out here about it.
>
> On Mar 14, 10:16 am, Sekhar  wrote:
> > We're getting a series of memcache issues. Anyone else? This after many
> > data store errors yesterday.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[alex]

"Waiting for a an API call could lower CPU" - well, that depends. If you're 
running in threadsafe mode enabled then yes, maybe.

Total CPU means exactly what it says: total, i.e. API calls + your app code 
CPU. Say, if you have a Total CPU of 1ms and the blue line is at 
9900ms, that means only 100ms were used for a service API call. The rest is 
somewhere very close to your app. 

At least, that's my understanding. 

Another example of a (very unexpected) error I've seen quite often is this: 
"'ascii' codec can't decode byte 0xe9 in position 0: ordinal not in 
range(128)". This, again, error in the app code. The developer completely 
forgot that we have different encodings. The app was working just fine for 
months, and it just happend that one day a non-US user signed up with a 
name that contained non ascii chars.

Have you tried to run your app with AppStats and see where it's taking most 
of the CPU?


On Wednesday, March 14, 2012 6:50:10 PM UTC+1, Mos wrote:
>
> Thanks for your thoughts
>
> > In fact, in your graphs the API calls CPU is as low as it always was
>
> CPU for API calls is not related to latency and timeouts, right? To the 
> contrary:  Waiting for a an API call could lower CPU, doesn't it?
> --> It seems not to help for this analysis
>
> >  ... using (e.g. URLfetch). ...  re-populating (re-caching)
>
> No nothing of these.
>
> > Well, I don't personally think that every filed ticket means a real 
> issue ...
>
> Please check the Outage-Thread and the other posting the last hours/days. 
> It's really obvious that something is going on.
>
> Cheers 
> Mos
>
>
>
> On Wed, Mar 14, 2012 at 6:38 PM, alex  wrote:
>
>> Well, I don't personally think that every filed ticket means a real 
>> issue. It often happens that the issue is in the code or something else, 
>> unrelated.
>>
>> In fact, in your graphs the API calls CPU is as low as it always was. 
>> That means the cause is neither Datastore, nor Memcache or any other 
>> service your app might be using (e.g. URLfetch). 
>>
>> Most likely that means the actual code of your app is consuming the CPU, 
>> so the scheduler simply launches more instances because the average latency 
>> of your app has increased. 
>>
>> Even though the traffic to your app is the same as it was before, it very 
>> much might be that your code is not covering all edge cases. I don't know, 
>> some missing entity property that happend to be there only in the past 24 
>> hours, or maybe you rely on memcached query results that are not there 
>> anymore and you just not re-populating (re-caching) some of it. Stuff like 
>> that.
>>
>>
>> On Wednesday, March 14, 2012 6:15:47 PM UTC+1, Mos wrote:
>>>
>>> Hi Alex,
>>>
>>> right, 1 instance is billed, cause this application runs in non payed 
>>> mode, but the scheduler spans up to four instances (without real need).
>>> In payed mode I assume the green line would not be on 1 instance all the 
>>> time...  (I'm glad I didn't activate payment yet)
>>>
>>> Graphs are attached.
>>>
>>> According to Google Analytic and application logging there was similar 
>>> usages then the days before.  (Around one to two request the minute)
>>> I think we don't need to discuss that something bad is going on the last 
>>> 24h to 48h hours for many GAE users?
>>> Please check issue tickets and other postings here.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:
>>>
 Funny... maybe I'm not getting something here but, where's the issue? 
 It is crystal clear from your graphs that you are being billed for 1 
 instance only, all the times.

 Can you show CPU ms used/sec and Errors/sec graphs?


 On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:
>
> And here are two that are related to this thread  (application has 
> same traffic, load and configuration for days  --> major GAE problem for 
> more then 24 hours):
>
> Attached
>
>
>
>
>
>>
>>
>> On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz 
>> wrote:
>>
>>> Nah it is all shiny… And that couple of hours when there are no 
>>> logs, that was just cause everyone was sleeping… 
>>>
>>> This is just a pretty picture… It’s not related to this thread. J
>>>
>>>  
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To post to this group, send email to google-appengine@googlegroups.*
>>> ***com .
>>> To unsubscribe from this group, send email to 
>>> google-appengine+unsubscribe@**g**ooglegroups.com
>>> .
>>> For more options, visit this group at http://groups.google.com/**
>>> group**/google-appengine?hl=en
>>> .
>>>
>>
>>
>
>  -- 
 You received this message because you are subscribed to the Google 
 Groups "Google App Engine

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Mos]

Thanks for your thoughts

> In fact, in your graphs the API calls CPU is as low as it always was

CPU for API calls is not related to latency and timeouts, right? To the
contrary:  Waiting for a an API call could lower CPU, doesn't it?
--> It seems not to help for this analysis

>  ... using (e.g. URLfetch). ...  re-populating (re-caching)

No nothing of these.

> Well, I don't personally think that every filed ticket means a real issue
...

Please check the Outage-Thread and the other posting the last hours/days.
It's really obvious that something is going on.

Cheers
Mos



On Wed, Mar 14, 2012 at 6:38 PM, alex  wrote:

> Well, I don't personally think that every filed ticket means a real issue.
> It often happens that the issue is in the code or something else, unrelated.
>
> In fact, in your graphs the API calls CPU is as low as it always was. That
> means the cause is neither Datastore, nor Memcache or any other service
> your app might be using (e.g. URLfetch).
>
> Most likely that means the actual code of your app is consuming the CPU,
> so the scheduler simply launches more instances because the average latency
> of your app has increased.
>
> Even though the traffic to your app is the same as it was before, it very
> much might be that your code is not covering all edge cases. I don't know,
> some missing entity property that happend to be there only in the past 24
> hours, or maybe you rely on memcached query results that are not there
> anymore and you just not re-populating (re-caching) some of it. Stuff like
> that.
>
>
> On Wednesday, March 14, 2012 6:15:47 PM UTC+1, Mos wrote:
>>
>> Hi Alex,
>>
>> right, 1 instance is billed, cause this application runs in non payed
>> mode, but the scheduler spans up to four instances (without real need).
>> In payed mode I assume the green line would not be on 1 instance all the
>> time...  (I'm glad I didn't activate payment yet)
>>
>> Graphs are attached.
>>
>> According to Google Analytic and application logging there was similar
>> usages then the days before.  (Around one to two request the minute)
>> I think we don't need to discuss that something bad is going on the last
>> 24h to 48h hours for many GAE users?
>> Please check issue tickets and other postings here.
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:
>>
>>> Funny... maybe I'm not getting something here but, where's the issue? It
>>> is crystal clear from your graphs that you are being billed for 1 instance
>>> only, all the times.
>>>
>>> Can you show CPU ms used/sec and Errors/sec graphs?
>>>
>>>
>>> On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:

 And here are two that are related to this thread  (application has same
 traffic, load and configuration for days  --> major GAE problem for more
 then 24 hours):

 Attached





>
>
> On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz wrote:
>
>> Nah it is all shiny… And that couple of hours when there are no logs,
>> that was just cause everyone was sleeping…
>>
>> This is just a pretty picture… It’s not related to this thread. J
>>
>>
>>
>>  --
>> You received this message because you are subscribed to the Google
>> Groups "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.**
>> **com .
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscribe@**g**ooglegroups.com
>> .
>> For more options, visit this group at http://groups.google.com/**
>> group**/google-appengine?hl=en
>> .
>>
>
>

  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google App Engine" group.
>>> To view this discussion on the web visit https://groups.google.com/d/**
>>> msg/google-appengine/-/tk8Xo_**fvQ04J
>>> .
>>>
>>> To post to this group, send email to 
>>> google-appengine@googlegroups.**com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscribe@**googlegroups.com
>>> .
>>> For more options, visit this group at http://groups.google.com/**
>>> group/google-appengine?hl=en
>>> .
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/9EjTUlYsfnQJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine"

RE: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Brandon Wirtz]

Non-payed apps have rules all of their own, they get slow sometimes for no
reason. I would not say this is an issue, it just is you are in the lowest
tier so if you get squished no one cares..

 

I think QoS/QoE is set this way on purpose.

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Mos
Sent: Wednesday, March 14, 2012 10:16 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] More then 100 complains and no feedback from
Google. Was: Outages?

 

Hi Alex,

right, 1 instance is billed, cause this application runs in non payed mode,
but the scheduler spans up to four instances (without real need).
In payed mode I assume the green line would not be on 1 instance all the
time...  (I'm glad I didn't activate payment yet)

Graphs are attached.

According to Google Analytic and application logging there was similar
usages then the days before.  (Around one to two request the minute)
I think we don't need to discuss that something bad is going on the last 24h
to 48h hours for many GAE users?
Please check issue tickets and other postings here.








On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:

Funny... maybe I'm not getting something here but, where's the issue? It is
crystal clear from your graphs that you are being billed for 1 instance
only, all the times.

 

Can you show CPU ms used/sec and Errors/sec graphs?



On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:

And here are two that are related to this thread  (application has same
traffic, load and configuration for days  --> major GAE problem for more
then 24 hours):

Attached









On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz  wrote:

Nah it is all shiny. And that couple of hours when there are no logs, that
was just cause everyone was sleeping. 

This is just a pretty picture. It's not related to this thread. J

 



-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
 .
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

 

 

 

-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.

To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/tk8Xo_fvQ04J.


To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
 .
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

 

-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[alex]

Well, I don't personally think that every filed ticket means a real issue. 
It often happens that the issue is in the code or something else, unrelated.

In fact, in your graphs the API calls CPU is as low as it always was. That 
means the cause is neither Datastore, nor Memcache or any other service 
your app might be using (e.g. URLfetch). 

Most likely that means the actual code of your app is consuming the CPU, so 
the scheduler simply launches more instances because the average latency of 
your app has increased. 

Even though the traffic to your app is the same as it was before, it very 
much might be that your code is not covering all edge cases. I don't know, 
some missing entity property that happend to be there only in the past 24 
hours, or maybe you rely on memcached query results that are not there 
anymore and you just not re-populating (re-caching) some of it. Stuff like 
that.


On Wednesday, March 14, 2012 6:15:47 PM UTC+1, Mos wrote:
>
> Hi Alex,
>
> right, 1 instance is billed, cause this application runs in non payed 
> mode, but the scheduler spans up to four instances (without real need).
> In payed mode I assume the green line would not be on 1 instance all the 
> time...  (I'm glad I didn't activate payment yet)
>
> Graphs are attached.
>
> According to Google Analytic and application logging there was similar 
> usages then the days before.  (Around one to two request the minute)
> I think we don't need to discuss that something bad is going on the last 
> 24h to 48h hours for many GAE users?
> Please check issue tickets and other postings here.
>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 5:58 PM, alex  wrote:
>
>> Funny... maybe I'm not getting something here but, where's the issue? It 
>> is crystal clear from your graphs that you are being billed for 1 instance 
>> only, all the times.
>>
>> Can you show CPU ms used/sec and Errors/sec graphs?
>>
>>
>> On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:
>>>
>>> And here are two that are related to this thread  (application has same 
>>> traffic, load and configuration for days  --> major GAE problem for more 
>>> then 24 hours):
>>>
>>> Attached
>>>
>>>
>>>
>>>
>>>


 On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz wrote:

> Nah it is all shiny… And that couple of hours when there are no logs, 
> that was just cause everyone was sleeping… 
>
> This is just a pretty picture… It’s not related to this thread. J
>
>  
>
>  -- 
> You received this message because you are subscribed to the Google 
> Groups "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.**
> com .
> To unsubscribe from this group, send email to 
> google-appengine+unsubscribe@**googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/**
> group/google-appengine?hl=en
> .
>


>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/google-appengine/-/tk8Xo_fvQ04J.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/9EjTUlYsfnQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[alex]

Funny... maybe I'm not getting something here but, where's the issue? It is 
crystal clear from your graphs that you are being billed for 1 instance 
only, all the times.

Can you show CPU ms used/sec and Errors/sec graphs?


On Wednesday, March 14, 2012 5:50:04 PM UTC+1, Mos wrote:
>
> And here are two that are related to this thread  (application has same 
> traffic, load and configuration for days  --> major GAE problem for more 
> then 24 hours):
>
> Attached
>
>
>
>
>
>>
>>
>> On Wed, Mar 14, 2012 at 5:29 PM, Brandon Wirtz wrote:
>>
>>> Nah it is all shiny… And that couple of hours when there are no logs, 
>>> that was just cause everyone was sleeping… 
>>>
>>> This is just a pretty picture… It’s not related to this thread. J
>>>
>>>  
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To post to this group, send email to google-appengine@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> google-appengine+unsubscr...@googlegroups.com.
>>> For more options, visit this group at 
>>> http://groups.google.com/group/google-appengine?hl=en.
>>>
>>
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/tk8Xo_fvQ04J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Problem with mail quota

[Christina Ilvento]

Hi All,

We recently made a change that causes the 100 email/day quota to only be
lifted once a charge has been successfully cleared. Did you recently enable
billing, or has billing been enabled for more than one week?


Thanks,
Christina

On Tue, Mar 13, 2012 at 8:46 PM, Daniel  wrote:

> I'm seeing the same problem! I have hit 100 emails and can't mail anymore
> even with a very generous billing quota per day.. billable email is not
> triggering.
>
> My app is sky-words-hrd
>
>
>
> On Wednesday, February 8, 2012 2:36:40 PM UTC-8, Ice13ill wrote:
>>
>> In SDK 1.6.2 is stated that:
>>  "Mail Quota for App Engine apps that have signed up for billing
>> will only be increased after the first payment for the app is
>> processed. "
>>
>> In the documentation I found this:
>> "100 recipients until first charge cleared; 2000 recipients free and
>> no maximum thereafter"
>>
>> The problem is that my app has billing enabled for a very long time
>> and although everything was ok until today (i also checked the billing
>> history and emails that exceeded the 100 limit were billed
>> correctly) , now my app has reached 100 mail quota and it cannot send
>> any more emails...
>>
>> Does anyone else has this problem ?
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/AYlR59U_ChkJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 

Christina Ilvento | Google App Engine | cilve...@google.com | (650)-201-9399

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[alex]

same here.




On Wednesday, March 14, 2012 5:29:58 PM UTC+1, Brandon Wirtz wrote:
>
> Nah it is all shiny… And that couple of hours when there are no logs, that 
> was just cause everyone was sleeping… 
>
> This is just a pretty picture… It’s not related to this thread. J
>
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/US9cOOFa7QYJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

RE: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Brandon Wirtz]

Nah it is all shiny. And that couple of hours when there are no logs, that
was just cause everyone was sleeping. 

This is just a pretty picture. It's not related to this thread. J

 



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>

[google-appengine] Re: Memcache issues 3/14

[agp]

I am too, I just put a different post out here about it.

On Mar 14, 10:16 am, Sekhar  wrote:
> We're getting a series of memcache issues. Anyone else? This after many
> data store errors yesterday.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] SITE SLOW AND DOWN

[agp]

I am getting a ton of issues like this today making the site basicly
down because they get a error page  with a stack trace (pasted below):

2012-03-14 10:41:34.194 [s~madisonpsa/8.356247106902853044].:
[ERROR] CacheServiceImpl - -Memcache put: Error setting single item
(org.vosao.entity.LanguageEntitygetB
W 2012-03-14 10:41:52.539 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (entity:org.vosao.entity.TemplateEnt
W 2012-03-14 10:41:57.460 [s~madisonpsa/
8.356247106902853044].: [INFO] PluginClassLoader - -creating
class loader sitemap
W 2012-03-14 10:42:01.778 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Set failed to set 1 keys: entity:org.vosao.entity.PluginResour
W 2012-03-14 10:42:02.783 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (sitemappluginResourceList)
W 2012-03-14 10:42:05.278 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Set failed to set 1 keys: entity:org.vosao.entity.PluginResour
W 2012-03-14 10:42:07.145 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (org.vosao.plugins.sitemap.SitemapVe
W 2012-03-14 10:42:09.108 [s~madisonpsa/
8.356247106902853044].: [INFO] PluginClassLoader - -creating
class loader superfish
W 2012-03-14 10:42:12.892 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (org.vosao.entity.PluginResourceEnti
W 2012-03-14 10:42:14.646 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl -
-Memcache put: Error setting single item (superfishpluginResourceList)
W 2012-03-14 10:42:15.650 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (org.vosao.plugins.superfish.Superfi
W 2012-03-14 10:42:20.731 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (superfishpluginResourceList)
W 2012-03-14 10:42:21.734 [s~madisonpsa/
8.356247106902853044].: [ERROR] CacheServiceImpl - -Memcache
put: Error setting single item (org.vosao.plugins.superfish.Superfi
W 2012-03-14 10:42:24.521 [s~madisonpsa/
8.356247106902853044].: [ERROR] QueryCacheImpl - -
com.google.apphosting.api.DeadlineExceededException: This request
(2b3888250c4
W 2012-03-14 10:42:24.522 [s~madisonpsa/
8.356247106902853044].:
W 2012-03-14 10:42:25.113 Error for /
com.google.apphosting.runtime.HardDeadlineExceededError: This request
(2b3888250c44649b) started at 2012/03/14 15:41:24.773 UTC and was st
C 2012-03-14 10:42:25.120 Uncaught exception from servlet
com.google.apphosting.runtime.HardDeadlineExceededError: This request
(2b3888250c44649b) started at 2012/03/14 15:41:2
I 2012-03-14 10:42:25.124 This request caused a new process to be
started for your application, and thus caused your application code to
be loaded for the first time. This requ
W 2012-03-14 10:42:25.124 A problem was encountered with the process
that handled this request, causing it to exit. This is likely to cause
a new process to be used for the nex



Error Page:
Uncaught exception from servlet
com.google.apphosting.api.ApiProxy$CancelledException: The API call
datastore_v3.Put() was explicitly cancelled.
at com.google.apphosting.runtime.ApiProxyImpl$5.get(ApiProxyImpl.java:
359)
at com.google.apphosting.runtime.ApiProxyImpl$5.get(ApiProxyImpl.java:
357)
at
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:
90)
at com.google.appengine.api.datastore.FutureHelper
$CumulativeAggregateFuture.get(FutureHelper.java:145)
at
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:
90)
at
com.google.appengine.api.datastore.FutureHelper.getInternal(FutureHelper.java:
72)
at
com.google.appengine.api.datastore.FutureHelper.quietGet(FutureHelper.java:
33)
at com.google.appengine.api.datastore.DatastoreServiceImpl
$2.runInternal(DatastoreServiceImpl.java:113)
at com.google.appengine.api.datastore.DatastoreServiceImpl
$2.runInternal(DatastoreServiceImpl.java:110)
at
com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:
31)
at
com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:
110)
at
com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:
94)
at
com.google.apphosting.runtime.jetty.DatastoreSessionStore.saveSession(DatastoreSessionStore.java:
93)
at com.google.apphosting.runtime.jetty.SessionManager
$AppEngineSession.save(SessionManager.java:164)
at
com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:
41)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.apphosting.utils.servlet.TransactionClean

[google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Mos]

Problem still exists: High latency and a significant number of requests
fail or result in uncontrolled creation of new instances.

GAE customers complain and complain for days.  It seems like many website
have to accept that the 500-error is an integral feature of the GAE
run-time.
Even worse:  The broken platform leads to increase usage of instances and
therefore leads to higher costs for paying customer.

No communication from Google; no feedback on the mailing list; no status
updates on the issue tracker.
Instead a always green status:   http://code.google.com/status/appengine
(I think the GAE community needs to develop a crowed sources status page to
get a picture what's really is going on)

That makes me crazy.  I saw many platforms and business support forums the
last years, but never encountered such an ignorance regarding custom
complains.

The only official response I saw, was the "Escalated your issue to the
reliability team" in one of the related issues:
http://code.google.com/p/googleappengine/issues/detail?id=7133

So, 'realiability team' what's going on? How is the status?



On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:

> > What is your application id?
>
> krisen-talk(www.krisentalk.de)
>
>
> > Feel free to open a production issue
>
> There is already an issue from someone else (following this thread a lot
> of people are affected):
>
> http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> Johan, what's going on with GAE the last days?  It doesn't feel like a
> PaaS in production mode.
> Perhaps Google should reintroduce the Beta status. ;)
>
>
> On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:
>
>> What is your application id?
>>
>> Feel free to open a production issue, if you want to investigate this
>> offthread:
>>
>> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>>
>>
>> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>>
>>> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
>>> instance, no new deployment, simple page just hitting MemCache):
>>>
>>> "Request was aborted after waiting too long to attempt to service your
>>> request."   -->  User sees 500er
>>>
>>> GAE-Team, what is going on the last days?  In my opinion the Google App
>>> Engine is unreliable and looks more like a alpha- or beta-
>>> cloudenvrionment
>>>
>>> Please Google share you analysis with us.
>>>
>>> Cheers
>>> Mos
>>>
>>>
>>>
>>>
>>>
>>> 2012/3/13 Sébastien Tromp 
>>>
 Hello,

 Same thing here, since around an hour ago:
 AppID: fiveorbsgame & fiveorbsgame-test


 On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:

> I'm encountering the same issue with HR app. The spike got started in
> about ~1 hour from now.
>
> AppID: cmsevobg
> Datastore: HR
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally
>> cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead
>> of e.g. 300ms) lately and sometimes higher error rates (a few instead of
>> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests that
>> threw 500's with accompanying messages [1], usually on memcache sets
>> hitting a deadline exceeded.  Also, over the last couple weeks I've been
>> running 3 instances permanently despite sometimes shutting them down
>> manually.  Usually I get by on one just fine with bursts of 2 or 3.  I've
>> noticed that one instance serves the majority of traffic with the other 
>> two
>> serving maybe 50 requests over many hours, so the shutdown isn't 
>> aggressive
>> enough.
>>
>> "This request caused a new process to be started for your
>> application..."
>> +
>> "A problem was encountered with the process that handled this
>> request, causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally
>> cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead
>> of e.g. 300ms) lately and sometimes higher error rates (a few instead of
>> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests that
>> threw 500's with accompanying messages [1], usually on memcache sets
>> hitting a deadline exceeded.  Also, over the last couple weeks I've been
>> running 3 instances permanently despite sometimes shutting them down
>> manually.  Usually I get by on one just fine with bursts of 2 or 3.  I've
>> noticed that one instance serves the majority of traffic with the other 
>> two
>> serving maybe 50 requests over many hours, so the shutdown isn't 
>> aggressive
>> enough.
>>
>> "This request caused a new process 

[google-appengine] Memcache issues 3/14

[Sekhar]

We're getting a series of memcache issues. Anyone else? This after many 
data store errors yesterday.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/UsFMzZXPPPUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Jeff Schnitzer]

On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
>
> On Mar 14, 1:17 pm, Gopal Patel  wrote:
>> you mean, always have one instance more than required ? ( who is going to
>> pay for that ? ) , and is not minimum idle instance same thing ?
>
> It is different with the normal resident instance.
> It is an instance to handle requests only at the time of the situation
> "no available instances and need create a new instance",
> so that many "Cold Starts" can be avoided.

This is pretty much exactly what setting minimum idle instances does.
Requests are preferentially routed to dynamic instances rather than
resident instances.

The problem is, something in the scheduler is broken.  Instead of
routing requests to the idle instance, GAE prefers to route requests
to a fresh instance, causing the user to wait while an instance warms
up.  That setting is probably best described as "minimum useless
instances".  Maybe somebody took the "minimum _idle_ instances" label
too literally ;-)

This is the behavior I observed a week or two ago.  Hopefully it will
be fixed.  Doesn't sound like it has been so far.

Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: High Replication latencies and it's related costs.

[andidol]

Have the same problem. HR datastore is very slow since yesterday..

On Wednesday, March 14, 2012 5:17:47 AM UTC+1, thecheatah wrote:
>
> Hi, 
>
> I am noticing that the latency on my HR based application went up 
> significantly. My app does a simple read and a write. It is taking 
> over 1 second to do this operation. In M/S the this operation was < 
> 100ms 
>
> Even under multi threading, my machines are not processing as many 
> requests as my M/S app could handle. My costs have gone up by 50% 
> after having switched from M/S. Is this normal? 
>
> Last night a single machine handled about 6-7 requests/second. Today 
> it has dropped to 4. Nothing has changed. The request are generated by 
> devices and thus are very consistent. 
>
> It seems that the latency on the HR datastore is causing my cost to 
> increase. I have no control over this latency. Is this something I can 
> get money back for? 
>
> Ravneet

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Jy8un6pwRu8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Very high latency since March 13th

[andidol]

Hi,

I have very high latency on my AppEngine since yesterday. It was really 
fast before < 100ms. Now there are a lot of requests performing with > 
200ms without any reason. I did not update or did anything.
I'm using High Replication Datastore.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/UKDaOm5bNJsJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: How to secure the SDK

[Barry Hunter]

Can use the windows firewall
http://windows.microsoft.com/en-GB/windows-vista/Open-a-port-in-Windows-Firewall

to open the port - and configure who can access it.

Its probably worth using a non default port (ie not 80) - to make it
harder for people to find. (the dev server allows you to choose a port
at startup)


On Wed, Mar 14, 2012 at 11:01 AM, Kaan Soral  wrote:
> Great idea
>
> What would be an easy solution to permit access for only a range of IP's?
> Preferrably with logging etc to deny first and allow later.
> On windows and for a network noob - This is probably not the right place for
> asking this but it would be great if any of you have suggestions
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/IGQV9BWzPEsJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: How to secure the SDK

[Kaan Soral]

Great idea

What would be an easy solution to permit access for only a range of IP's? 
Preferrably with logging etc to deny first and allow later.
On windows and for a network noob - This is probably not the right place 
for asking this but it would be great if any of you have suggestions

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/IGQV9BWzPEsJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Design problem - How to avoid datastore contention

[Sahid Orentino Ferdjaoui]

Hi all

I have a question on stackoverflow about avoiding datastore contention, if 
anybody can help me.

http://stackoverflow.com/questions/9700388/avoiding-datastore-contention

Thanks a lot!


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/-kEBUznzgxsJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: How to secure the SDK

[Aidan O'Kelly]

Still should be a network security concern, ie, setup a secure vpn, or
allow limited access to a range of IP's through your firewall.
The java version of the SDK at least, has a -bindAddress option. Binding to
127.0.0.1 will mean the server will only listen for requests from your
machine. (It set itself up like this by default for me)

Anyway, if you run any kind of developer sdk server and allow access to the
outside world you are asking for trouble, since they are never written with
the intention of being a secure production server.

On Wed, Mar 14, 2012 at 9:48 AM, Kaan Soral  wrote:

> Why? - because sometimes you have to work with external systems and they
> have to work with you - even on the development level
>
>
> On Wednesday, March 14, 2012 10:42:59 AM UTC+2, Simon Knott wrote:
>>
>> Why would your SDK be available to the outside world?  It's a development
>> tool, no different to any development environments - lock it down via the
>> network infrastructure, as you would any other development environment.  If
>> you have production data in your dev environment and it contains sensitive
>> data, then take the normal steps to sanitise it.
>>
>> On Tuesday, 13 March 2012 20:50:01 UTC, Kaan Soral wrote:
>>>
>>> If the SDK is accessible to the outer world, it poses a HUGE security
>>> risk
>>>
>>> One can simply write a script for "Interactive 
>>> Console"
>>> and steal all your code/data
>>>
>>> To prevent this - one may restrict access to Development Console and
>>> permit only 127.0.0.1, this can be easily done by modifying the Handlers of
>>> the Development Console
>>>
>>> Can you guys think of any other security holes?
>>>
>>> I've been meaning to ask this for a long time, but at the same time I
>>> didn't want to attract anyone to exploit these risks - but here it is anyway
>>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/kW20c_wtRsMJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: How to secure the SDK

[Kaan Soral]

Why? - because sometimes you have to work with external systems and they 
have to work with you - even on the development level

On Wednesday, March 14, 2012 10:42:59 AM UTC+2, Simon Knott wrote:
>
> Why would your SDK be available to the outside world?  It's a development 
> tool, no different to any development environments - lock it down via the 
> network infrastructure, as you would any other development environment.  If 
> you have production data in your dev environment and it contains sensitive 
> data, then take the normal steps to sanitise it.
>
> On Tuesday, 13 March 2012 20:50:01 UTC, Kaan Soral wrote:
>>
>> If the SDK is accessible to the outer world, it poses a HUGE security risk
>>
>> One can simply write a script for "Interactive 
>> Console" 
>> and steal all your code/data
>>
>> To prevent this - one may restrict access to Development Console and 
>> permit only 127.0.0.1, this can be easily done by modifying the Handlers of 
>> the Development Console
>>
>> Can you guys think of any other security holes?
>>
>> I've been meaning to ask this for a long time, but at the same time I 
>> didn't want to attract anyone to exploit these risks - but here it is anyway
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/kW20c_wtRsMJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: How to secure the SDK

[Simon Knott]

Why would your SDK be available to the outside world?  It's a development 
tool, no different to any development environments - lock it down via the 
network infrastructure, as you would any other development environment.  If 
you have production data in your dev environment and it contains sensitive 
data, then take the normal steps to sanitise it.

On Tuesday, 13 March 2012 20:50:01 UTC, Kaan Soral wrote:
>
> If the SDK is accessible to the outer world, it poses a HUGE security risk
>
> One can simply write a script for "Interactive 
> Console" 
> and steal all your code/data
>
> To prevent this - one may restrict access to Development Console and 
> permit only 127.0.0.1, this can be easily done by modifying the Handlers of 
> the Development Console
>
> Can you guys think of any other security holes?
>
> I've been meaning to ask this for a long time, but at the same time I 
> didn't want to attract anyone to exploit these risks - but here it is anyway
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/5DxU7Rl8wMQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Nicanor Babula]

Now my app is working fine. What happened? I saw at some point my app's 
graphs reset and some huge values for instance hours values. Afterwards, 
the instance hours counters turned to normal and my app stpped raising 
errors. If there was the GAE team working on it, thank you very much, but I 
think you owe us at least an explanation. What should I say to my 
customers? The issue has been fixed or they should  be expecting outages in 
the following days? My app is on HRD.

Thanks,
Cristian

Il giorno martedì 6 marzo 2012 22:17:37 UTC+1, Adam Sherman ha scritto:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/hw3niAzjSIAJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Mos]

> Potential fix: set performance sliders to auto.

No, that doesn't help in general. I'm running from the start with auto and
having the problem.

It's still not fixed;  would be nice to get some feedback from Google ?!

On Wed, Mar 14, 2012 at 3:14 AM, Mauricio Aristizabal wrote:

> Potential fix: set performance sliders to auto.
>
> This is purely anecdotal but it might mean something:  After reading some
> post this afternoon about the instance settings not really working I
> switched to AUTO idle instances and AUTO pending latency (before they were
> set to 1-1 and 25ms-1.5s respectively).
>
> That was about 5 hours ago, and within an hour or so everything started
> working fine.  Before that, problems had been continuous as far as I could
> tell for 6 days or so.
>
> Or maybe the AppEngine guys finally got it under control.
>
>
>
> On Tue, Mar 13, 2012 at 5:58 PM, stephenp  wrote:
>
>> One more here.
>>
>> appid: carglyplatform (HRD)
>>
>> It's been flaky off-and-on for a couple weeks, yesterday was better,
>> today bad again. Lots of warmup errors, instance restarts, errors in
>> general.
>>
>> Stephen
>>
>>
>> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>>
>>> Am I the only one seeing short duration outages? They are being
>>> reflected at:
>>>
>>> http://code.google.com/status/**appengine
>>>
>>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>>
>>> A.
>>>
>>>
>> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>>
>>> Am I the only one seeing short duration outages? They are being
>>> reflected at:
>>>
>>> http://code.google.com/status/**appengine
>>>
>>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>>
>>> A.
>>>
>>>
>> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>>
>>> Am I the only one seeing short duration outages? They are being
>>> reflected at:
>>>
>>> http://code.google.com/status/**appengine
>>>
>>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>>
>>> A.
>>>
>>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/google-appengine/-/C5nrBOmPaPcJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Tapir]

On Mar 14, 1:17 pm, Gopal Patel  wrote:
> you mean, always have one instance more than required ? ( who is going to
> pay for that ? ) , and is not minimum idle instance same thing ?

It is different with the normal resident instance.
It is an instance to handle requests only at the time of the situation
"no available instances and need create a new instance",
so that many "Cold Starts" can be avoided.

"Who pay for that?"
If it is implemented cleverly, not many extra cost for Google.
And please consider the current instance prices is more than 5 times
higher than the normal level.

I said many times, the GAE instance scheduler program has problems.
Sometimes, even the normal resident instance is idle, GAE instance
scheduler will still not use it.
This means the normal resident instance is not always available for
your apps, the money you pays is wasted sometimes.

>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 10:36 AM, Tapir  wrote:
> > I means "why not to conquer it instead of trying to avoid it?".
>
> > If you can't conquer it, please lower the instance prices to the
> > normal level, I mean about tenth to fifth of the current level so that
> > apps can open more resident instances to avoid "Cold Starts".
>
> > Here is one solution: give each app one hidden resident instance, when
> > an app needs a new instance to handle a coming request, GAE use the
> > hidden resident instance to handle the coming request, and open the
> > new instance at the same time. Your current "open a new instance and
> > let the new coming request to be handled after the new instance is
> > warmed up" is not a good implementation.
>
> > On Mar 14, 11:51 am, Tapir  wrote:
> > > .
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Channel API is working locally But not in production throws provided token is invalid

[Andrin von Rechenberg]

BIG LETTERS SUCK.

File a production issue if you are sure that it's not your fault:
http://code.google.com/p/googleappengine/issues

On Tue, Mar 13, 2012 at 4:54 PM, praveen kumar  wrote:

>  I will create channel Id(token)  using Channel API in server side.,
> In the client side using this token while opening the channel using
> http://talkgadget.google.com/talkgadget/channel.js. It throwing error
> provider token is invalid .
>
> Please help how to fix this issue
>
> Regards.,
> Praveen.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.