[google-appengine] Re: GAE 1.6 can not import module jinja2

[Niklas Rosencrantz]

If you do 

import jinja2

you must download jinja2 and keep it in the app directory and it will work. 
The correct way of doing it however is to my knowledge

from webapp2_extras import jinja2

then you don't need the local library since you're importing from webapp2. 
It may depend on whether you want to use webapp2 or some other framework. I 
hope this works for you too.
Regards,
Nick

-- 
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/-/DETAhQ1Z5ZUJ.
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: GAE 1.6 can not import module jinja2

[steve]

I installed it locally and I am still unable to import jinja2, it is giving 
me the import jinja2 error every time.

-- 
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/-/TB85cNSg1cUJ.
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] Maximum length of query string in GET request

[Vivek Puri]

Can someone from AppEngine team please let me know what is the maximum
acceptable query_string length for GET requests using webapp
framework.


Thank you

-- 
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: fastest way to serialize db.Model(s) to json?

[Kyle Finley]

aschmid,

Are you running python27? If so you should see some improvement by 
importing *json* instead of *simplejson*. 

http://stackoverflow.com/a/8191970/236564

-- 
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/-/GFQ13LeHVP4J.
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: Unable to get dynamic backend to start on receiving browser request

[jon]

OK so this was due to my own misinterpretation of the doco.

I've created a ticket to remove ambiguity in the documentation.

http://code.google.com/p/googleappengine/issues/detail?id=6745&thanks=6745&ts=1326762667

On Jan 17, 5:43 am, Johan Euphrosine  wrote:
> What is your application id ?
>
>
>
>
>
>
>
>
>
> On Mon, Jan 16, 2012 at 2:17 PM, jon  wrote:
> > Upgrated to GAE/J 1.6.1.1. Still no luck. Anybody?
>
> > On Jan 16, 5:13 pm, jon  wrote:
> > > Hi,
>
> > > I've read and re-read the documentation and have tried various things
> > > but I haven't been able to get dynamic backend to start automatically
> > > on receiving user request.
>
> > > Here's my config:
>
> > > 
> > >   
> > >     B2
> > >     1
> > >     
> > >       true
> > >       true
> > >     
> > >   
> > > 
>
> > > When I hit backenda.myapp.appspot.com I always get a 503 error with
> > > the following error message:
>
> > > Error: Server Error
>
> > > The service you requested is not available yet.
> > > Please try again in 30 seconds.
>
> > > 
>
> > > Am I missing something? I'm still on GAE/J 1.5.5.
>
> > --
> > 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.
>
> --
> Johan Euphrosine (proppy)
> Developer Programs Engineer
> Google Developer Relations

-- 
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: fastest way to serialize db.Model(s) to json?

[Andreas]

yes i did for my rpc calls im actually handling myself atm. 
i didn't look at how it serializes objects but i doubt it does something 
different than looping over the properties and serializing them like my other 
function does but i might be wrong.

ill check it out tomorrow i think.

On Jan 16, 2012, at 6:50 PM, alex wrote:

> aschmid, this might be useless to you but if it's an API-related thing you're 
> serializing, have you considered ProtoRPC? 
> http://code.google.com/appengine/docs/python/tools/protorpc/overview.html
> 
> -- 
> 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/-/Io3crXFlGdsJ.
> 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: fastest way to serialize db.Model(s) to json?

[alex]

aschmid, this might be useless to you but if it's an API-related thing 
you're serializing, have you considered 
ProtoRPC? 
http://code.google.com/appengine/docs/python/tools/protorpc/overview.html

-- 
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/-/Io3crXFlGdsJ.
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] Potentially blocking issues as we near production: TLS/SSL, POST/PUT chunked encoding, support options

[Cayden Meyer]

Hi Jonathan,

Glad to hear that you have enjoyed using App Engine for development of your
application.

Issues 1:
I very much understand how important SSL is for App Engine users and we
have been trying to get as many users as we can into the Trusted Tester
Program.

We have had a huge number of applicants and we have been slowly ramping up
the number of users we add to the program. The Trusted Tester Program is
aimed at gaining feedback from users and identifying and fixing issues
before we roll the service out to a larger audience. By adding all the
users that applied to the program we would have greater difficulty
in achieving all of these goals.

This being said we should be adding a small number of new testers later
this week and I will try and get you added to this group.

Issue 2:
I would also recommend running a testing version on App Engine if you need
chunked transfer encoding for testing.

On your concern for removing support for chunked encoding, we have no plans
to do so and I doubt we would have any plans to remove it in the future. We
also have a three year deprecation policy for General Availability features
(this excludes experimental and Trusted Tester obviously) so even if we did
decide to remove it or any other feature you could still use it for three
years.

We are always trying to improve the developer experience, fixing bugs in
dev appserver is very much included in this.

Issues 3:
Our premier accounts gives you more than just access to Google Engineers
for support. Premier customers also receive a monthly invoice and can
create an unlimited number of applications without a minimum monthly spend.

To clarify, high priority issues have a response time target of 4 hours.
Lower priority requests have a response target of 1 business day or less.
For more information you can see
here
.

Hope that clears up your concerns,

Cayden Meyer
Product Manager, Google App Engine

On 17 January 2012 02:28, Jonathan Layes  wrote:

> Hi folks,
>
> Our team has been developing a product for about a year on app engine
> (Java) and we've been very happy with it as a development platform.
> However, I have now reached a point where I need to decide if we can stay
> on GAE as we move closer to production. At the moment, there are three
> issues that could block us moving to production on GAE:
>
> 1) TLS/SSL support for custom domains: This has been asked by many others
> and I know Google's policy is not to provide release dates. However, this
> really is a showstopper for us. We cannot move to production on GAE without
> TLS support on our domain. I applied for the TLS Trusted Tester program
> about two months ago but I have not heard anything in response. Is there
> any way to determine where a Trusted Tester application is in the queue?
>
> 2) Chunked encoding on PUT or POST body: For some reason, the development
> server in Java does not accept a chunked transfer encoding for PUT or POST
> requests (it returns 411 length required errors). Fortunately, the GAE
> frontend does not suffer from this limitation; the problem only occurs in
> development (and we have workarounds). However, given that the Python folks
> also report this problem in development (see
> http://code.google.com/p/googleappengine/issues/detail?id=129), I would
> feel more comfortable moving to production on GAE if someone at Google
> could state that you intend to continue supporting chunked transfer
> encoding for PUT/POST requests. Our application cannot determine the length
> of the POST request body in advance and relies on chunked encoding. The
> HTTP 1.1 specification requires support of chunked encoding and so I'm not
> sure why the development servers fail to support a chunked transfer
> encoding.
>
> 3) Support options: (Not necessarily a showstopper but an important
> consideration) $500/month is rather pricey for a one-model-fits-all
> solution, especially when the response times are 24 hours and limited to
> weekdays. Compare that to even the Bronze $49/month for Amazon AWS (12 hour
> turnaround any day of the week) and, at least on paper, AWS appears to have
> both better and more affordable support options. Are there plans to provide
> other support plans in the future?
>
> Thanks, Jonathan
>
> --
> 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/-/mEbSHRP1TJsJ.
> 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 unsu

RE: [google-appengine] Re: Why are several production issues related to DeadlineExceededErrors being ignored?

[Brandon Wirtz]

If it is a software / configuration issue in your setup then it is not down
time.

If you have errors on M/S you are on your own.

Instances die early if you hit the soft memory limit. Likely if you have
load time issues you have memory usage issues as well.


-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Cezary Wagner
Sent: Monday, January 16, 2012 2:37 PM
To: Google App Engine
Subject: [google-appengine] Re: Why are several production issues related to
DeadlineExceededErrors being ignored?

Brandom,

I think that problem of DeadlinesExceeds is different:
1st of GAE availability is not measure considering DeadlinesExceeds - it
will be rather not 100%. If it not monitored it has not impact on quality.
Am I wrong?
This is data for the last week:
Day Total checksOutages Failed checks   Avg. response time
Uptime
2012.01.14  26  1   1   3.152   96.154 %
2012.01.15  47  1   1   4.937   97.872 %
2012.01.16  47  4   5   3.657   89.362 %

2nd My code without changes through months becomes slower/not faster - I
have optimized code and it works not faster - on SDK it executes 5s-1s
(excluding load time) see above results from production. It could be
suffered with imports but why it once loads and once not loads it random -
it should not load every time or it problem with balance/resource - why IT
IS RANDOM?

3rd Instance DIES just after load not survive 15min period - instance was
load for 1 min than it dies - that is some problem or lack of
balance/resource?

4rd Maybe master/slave has impact?

5th The application not works in my case under low traffic EARLY DIES of
INSTANCES and DeadlinesExceeds kills 3%-10% of customer traffic(stats above)
- I am imagine that GAE works some for higher traffic with exception that
number of errors will be lower - maybe - but how achieve high traffic if it
not works on lower?

Please answer to question or propose other solution - GAE concept is good
but the current my customers experience is not excellent.

On 16 Sty, 18:58, "Brandon Wirtz"  wrote:
> I agree multiple imports is not supposed to be a problem, but I have
> seen it cause issues, or seen issues be resolved by not doing it.
>
> Remember that the Google Implementation of Python has its own
"Specialness"
> and what is true in traditional python is not always quite the same in
> GAE land.
>
> From: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Karl Rosaen
> Sent: Monday, January 16, 2012 7:32 AM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Re: Why are several production issues
> related to DeadlineExceededErrors being ignored?
>
> Brandon, thanks so much for taking the time to put together the video,
> very helpful.
>
> The key insight seem to be: time spent in the queue waiting for a
> frontend counts towards the limit for a DeadlineExceedError.  This
> seems silly - seems to me user visible latency, and framework level
> timeout enforcement should be decoupled in this case.  But good
> insight and glad to better understand this behavior.  This also makes
> me wonder what the benefit of having 'auto' for max pending latency
> would ever be - I'm going to slide mine down to ~1s.
>
> One quibble about your advice for 'avoid importing code more than once':
> this shouldn't be a major issue in python unless you are importing a
> module from within a function that is called several times:
>
> Although Python's interpreter is optimized to not import the same
> module multiple times, repeatedly executing an import statement can
> seriously affect performance in some circumstances.
>
> http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Import_Statem...
> rhead
>
> Just wanted to clarify that one needn't fret about the same utility
> module being imported from two modules or anything like that.
>
> Karl
> --
> You received this message because you are subscribed to the Google
> Groups "Google App Engine" group.
> To view this discussion on the web
visithttps://groups.google.com/d/msg/google-appengine/-/7FTyQ34tagsJ.
> 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
athttp://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

Re: [google-appengine] Re: fastest way to serialize db.Model(s) to json?

[Andreas]

cant really believe this is the only solution. serializing objects is not an 
uncommon thing to do.
if this is the best and quickest way to serialize objects then i might really 
store not only a list of properties but the completely serialized object into a 
dictionary in the blobstore.

On Jan 10, 2012, at 3:09 PM, Gregory Nicholas wrote:

> if it's as bad as 6 to 8 seconds, have you looked at creating a list
> of string for the property names? i know its more maintenance
> overhead, but might be worth the tradeoff..
> 
> ex:
> 
> class SerializableModel(object):
> 
>  serializable = []
> 
>  def to_json(self):
>result = []
>for x in self.serializable:
>  result.append(self.__dict__[x])
>## append values from self.properties().items()
> 
> 
> class A(db.Model, SerializableModel):
>  serializable = ['user_keys']
>  _user_keys = db.StringListProperty(default=[], indexed=False)
> 
>  @property
>  def user_keys(self):
>return [db.Key(x) for x in self._user_keys]
> 
>  @property
>  def user_keys_count(self):
>"""not in serializable list"""
>return len(self._user_keys)
> 
> 
> 
> 
> On Jan 10, 9:05 am, Andreas  wrote:
>> hi,
>> 
>> im using more or less this 
>> (http://www.awebcoder.com/post/91001/extended-jsonify-function-for-app...) 
>> jsonify function to serialize whatever object i pass into the jsonify() 
>> function and i have to say it does all i need and works pretty good.
>> the only downside i see right now is the speed. if i try to serialize 50 
>> db.Model objects with around 10 properties each in production it takes 6-8 
>> seconds which is not exactly what i would expect.
>> 
>> is there a way to make this part of  code more performant?
>> for property in dir(obj):
>> if property[0] != '_':
>> try:
>> value = obj.__getattribute__(property)
>> valueClass = str(value.__class__)
>> if not(('function' in valueClass) or ('built' in valueClass) 
>> or ('method' in valueClass)):
>> value = dumps(value)
>> if value != None:
>> properties[property] = value
>> else:
>> properties[property] = ""
>> except: continue
>> if len(properties) == 0:
>> return str(obj)
>> else:
>> return properties
>> 
>> i know i could use obj.properties().items() to loop over the properties but 
>> i would not be able to serialize properties which are @property functions 
>> because those don't get listed in the obj.properties() list.
>> 
>> right now im caching the results so im gaining speed because i get the 
>> result from memcache but when i flush the cache or the memcached result is 
>> not available it takes too much until the result is ready.
>> 
>> thx
> 
> -- 
> 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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Cezary Wagner]

Brandom,

I think that problem of DeadlinesExceeds is different:
1st of GAE availability is not measure considering DeadlinesExceeds -
it will be rather not 100%. If it not monitored it has not impact on
quality. Am I wrong?
This is data for the last week:
Day Total checksOutages Failed checks   Avg. response time  Uptime
2012.01.14  26  1   1   3.152   96.154 %
2012.01.15  47  1   1   4.937   97.872 %
2012.01.16  47  4   5   3.657   89.362 %

2nd My code without changes through months becomes slower/not faster -
I have optimized code and it works not faster - on SDK it executes
5s-1s (excluding load time) see above results from production. It
could be suffered with imports but why it once loads and once not
loads it random - it should not load every time or it problem with
balance/resource - why IT IS RANDOM?

3rd Instance DIES just after load not survive 15min period - instance
was load for 1 min than it dies - that is some problem or lack of
balance/resource?

4rd Maybe master/slave has impact?

5th The application not works in my case under low traffic EARLY DIES
of INSTANCES and DeadlinesExceeds kills 3%-10% of customer
traffic(stats above) - I am imagine that GAE works some for higher
traffic with exception that number of errors will be lower - maybe -
but how achieve high traffic if it not works on lower?

Please answer to question or propose other solution - GAE concept is
good but the current my customers experience is not excellent.

On 16 Sty, 18:58, "Brandon Wirtz"  wrote:
> I agree multiple imports is not supposed to be a problem, but I have seen it
> cause issues, or seen issues be resolved by not doing it.
>
> Remember that the Google Implementation of Python has its own "Specialness"
> and what is true in traditional python is not always quite the same in GAE
> land.
>
> From: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Karl Rosaen
> Sent: Monday, January 16, 2012 7:32 AM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Re: Why are several production issues
> related to DeadlineExceededErrors being ignored?
>
> Brandon, thanks so much for taking the time to put together the video, very
> helpful.
>
> The key insight seem to be: time spent in the queue waiting for a frontend
> counts towards the limit for a DeadlineExceedError.  This seems silly -
> seems to me user visible latency, and framework level timeout enforcement
> should be decoupled in this case.  But good insight and glad to better
> understand this behavior.  This also makes me wonder what the benefit of
> having 'auto' for max pending latency would ever be - I'm going to slide
> mine down to ~1s.
>
> One quibble about your advice for 'avoid importing code more than once':
> this shouldn't be a major issue in python unless you are importing a module
> from within a function that is called several times:
>
> Although Python's interpreter is optimized to not import the same module
> multiple times, repeatedly executing an import statement can seriously
> affect performance in some circumstances.
>
> http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Import_Statem...
> rhead
>
> Just wanted to clarify that one needn't fret about the same utility module
> being imported from two modules or anything like that.
>
> Karl
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web 
> visithttps://groups.google.com/d/msg/google-appengine/-/7FTyQ34tagsJ.
> 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 
> athttp://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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Alexis]

Kenneth: I'm talking HRD

-- 
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] Statistics data remain after I delete entities.

[Mike_W]

Hi,
  I have delete 2.3M entities from my app.
However I still have 2.3M entities remaining almost all of which are
Statistics.

Is there a mechanism to remove the statistics in  parallel with the
entities?
They consume a lot of space.

Regards
Mike

-- 
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] Potentially blocking issues as we near production: TLS/SSL, POST/PUT chunked encoding, support options

[Brandon Wirtz]

If you would like you can send me $250 a month and I’ll take your call 24/7.
I’ll even pretend I care about your downtime, and that “we” are working to
resolve the issue.
 
This is 5x the price of Amazon, and ½ the price of google, but I’ll be more
responsive than Google, and less of a jerk than Amazon.  In either case the
fixes for your issues will be resolved in the same time frame as everyone
else because for the most part no one knows which physical machines your
stuff is running on or how to move it, if they are in fact acting weird.
 
Issue 2. Run on production in a test instance… 

Issue 3. Hybrid with Amazon to do reverse proxy, That way I can sell you
another $250 a month support contract for them as well J
 
All kidding aside, I don’t think support will increase your uptime. It might
help with your TLS/SSL issues. I often think the Dev Server has bugs
intentionally. I think complaining about them encourages them to leave them
in so they know how many people are running it.
 
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Jonathan Layes
Sent: Monday, January 16, 2012 7:28 AM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Potentially blocking issues as we near
production: TLS/SSL, POST/PUT chunked encoding, support options
 
Hi folks,

Our team has been developing a product for about a year on app engine (Java)
and we've been very happy with it as a development platform. However, I have
now reached a point where I need to decide if we can stay on GAE as we move
closer to production. At the moment, there are three issues that could block
us moving to production on GAE:

1) TLS/SSL support for custom domains: This has been asked by many others
and I know Google's policy is not to provide release dates. However, this
really is a showstopper for us. We cannot move to production on GAE without
TLS support on our domain. I applied for the TLS Trusted Tester program
about two months ago but I have not heard anything in response. Is there any
way to determine where a Trusted Tester application is in the queue?

2) Chunked encoding on PUT or POST body: For some reason, the development
server in Java does not accept a chunked transfer encoding for PUT or POST
requests (it returns 411 length required errors). Fortunately, the GAE
frontend does not suffer from this limitation; the problem only occurs in
development (and we have workarounds). However, given that the Python folks
also report this problem in development (see
http://code.google.com/p/googleappengine/issues/detail?id=129), I would feel
more comfortable moving to production on GAE if someone at Google could
state that you intend to continue supporting chunked transfer encoding for
PUT/POST requests. Our application cannot determine the length of the POST
request body in advance and relies on chunked encoding. The HTTP 1.1
specification requires support of chunked encoding and so I'm not sure why
the development servers fail to support a chunked transfer encoding.

3) Support options: (Not necessarily a showstopper but an important
consideration) $500/month is rather pricey for a one-model-fits-all
solution, especially when the response times are 24 hours and limited to
weekdays. Compare that to even the Bronze $49/month for Amazon AWS (12 hour
turnaround any day of the week) and, at least on paper, AWS appears to have
both better and more affordable support options. Are there plans to provide
other support plans in the future?

Thanks, Jonathan
-- 
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/-/mEbSHRP1TJsJ.
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] Potentially blocking issues as we near production: TLS/SSL, POST/PUT chunked encoding, support options

[Jonathan Layes]

Hi folks,

Our team has been developing a product for about a year on app engine 
(Java) and we've been very happy with it as a development platform. 
However, I have now reached a point where I need to decide if we can stay 
on GAE as we move closer to production. At the moment, there are three 
issues that could block us moving to production on GAE:

1) TLS/SSL support for custom domains: This has been asked by many others 
and I know Google's policy is not to provide release dates. However, this 
really is a showstopper for us. We cannot move to production on GAE without 
TLS support on our domain. I applied for the TLS Trusted Tester program 
about two months ago but I have not heard anything in response. Is there 
any way to determine where a Trusted Tester application is in the queue?

2) Chunked encoding on PUT or POST body: For some reason, the development 
server in Java does not accept a chunked transfer encoding for PUT or POST 
requests (it returns 411 length required errors). Fortunately, the GAE 
frontend does not suffer from this limitation; the problem only occurs in 
development (and we have workarounds). However, given that the Python folks 
also report this problem in development (see 
http://code.google.com/p/googleappengine/issues/detail?id=129), I would 
feel more comfortable moving to production on GAE if someone at Google 
could state that you intend to continue supporting chunked transfer 
encoding for PUT/POST requests. Our application cannot determine the length 
of the POST request body in advance and relies on chunked encoding. The 
HTTP 1.1 specification requires support of chunked encoding and so I'm not 
sure why the development servers fail to support a chunked transfer 
encoding.

3) Support options: (Not necessarily a showstopper but an important 
consideration) $500/month is rather pricey for a one-model-fits-all 
solution, especially when the response times are 24 hours and limited to 
weekdays. Compare that to even the Bronze $49/month for Amazon AWS (12 hour 
turnaround any day of the week) and, at least on paper, AWS appears to have 
both better and more affordable support options. Are there plans to provide 
other support plans in the future?

Thanks, Jonathan

-- 
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/-/mEbSHRP1TJsJ.
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: Time lag with logging

[Nijin Narayanan]

Hey,

Here is some points:-
http://code.google.com/p/googleappengine/issues/detail?id=5494
if you switch the logs to PST timezone, you do see all of them.

Cheers! ,

NN




On Mon, Jan 16, 2012 at 3:57 PM, Sagi  wrote:

> Happens to me as well and makes it really hard to see what's going on
> when troubleshooting issues.
>
>
> On Dec 7 2011, 2:55 am, Jane Abernethy 
> wrote:
> > Hi,
> >
> > I am noticing a bit of a time lag with logging - I'll log something, call
> > the method and the logs wont update for about 15 minutes. Is anyone else
> > experiencing this?
>
> --
> 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: GAE's http header length limit, bug or undocumented restriction?

[Brandon Wirtz]

I'd have to look it up, it came up a lot at Microsoft In the IPTV group.

-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of tempy
Sent: Monday, January 16, 2012 12:44 PM
To: Google App Engine
Subject: [google-appengine] Re: GAE's http header length limit, bug or
undocumented restriction?

Really? I tried to find something in the spec about header lengths and
didn't find anything. According to this thread:
http://stackoverflow.com/questions/686217/maximum-on-http-header-values
there are no maximums. And where did you get the 4k number? Thanks!

On Jan 16, 9:09 pm, "Brandon Wirtz"  wrote:
> 400 is the specification limit for http header elements.
> (actually I think it is 400 characters converted to Base64)
>
> Most things don't break if you go over this,
>
> The max size for all Http Headers is 4k
>
>
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of tempy
> Sent: Monday, January 16, 2012 10:40 AM
> To: Google App Engine
> Subject: [google-appengine] GAE's http header length limit, bug or
> undocumented restriction?
>
> Hi All,
>
> I've hit a behavior that doesn't exist on the dev-server, which is
> that custom http headers on the response seem to be limited to around
> 400 characters. One custom header that I'm using which is regularly
> about
> 700 chars is simply silently dropped from the response.
>
> Firstly - this restriction, if its not a bug, should be documented.
> I've spent a whole lot of time building a feature around a big http
> header which worked fine all along on the dev server, if I have to re-
> architect this feature then it'll be a few days of work down the tubes.
>
> Secondly - is this a bug? This
> issue:http://code.google.com/p/googleappengine/issues/detail?id=407
> Seems to indicate that this is a bug, but its marked as fixed and it
> is clearly not fixed. If it is a bug, is there a known workaround?
>
> It would be really great if someone from google could weigh in here.
> Thanks!
>
> --
> 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
athttp://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: GAE's http header length limit, bug or undocumented restriction?

[tempy]

Really? I tried to find something in the spec about header lengths and
didn't find anything. According to this thread:
http://stackoverflow.com/questions/686217/maximum-on-http-header-values
there are no maximums. And where did you get the 4k number? Thanks!

On Jan 16, 9:09 pm, "Brandon Wirtz"  wrote:
> 400 is the specification limit for http header elements.
> (actually I think it is 400 characters converted to Base64)
>
> Most things don't break if you go over this,
>
> The max size for all Http Headers is 4k
>
>
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of tempy
> Sent: Monday, January 16, 2012 10:40 AM
> To: Google App Engine
> Subject: [google-appengine] GAE's http header length limit, bug or
> undocumented restriction?
>
> Hi All,
>
> I've hit a behavior that doesn't exist on the dev-server, which is that
> custom http headers on the response seem to be limited to around
> 400 characters. One custom header that I'm using which is regularly about
> 700 chars is simply silently dropped from the response.
>
> Firstly - this restriction, if its not a bug, should be documented.
> I've spent a whole lot of time building a feature around a big http header
> which worked fine all along on the dev server, if I have to re- architect
> this feature then it'll be a few days of work down the tubes.
>
> Secondly - is this a bug? This 
> issue:http://code.google.com/p/googleappengine/issues/detail?id=407
> Seems to indicate that this is a bug, but its marked as fixed and it is
> clearly not fixed. If it is a bug, is there a known workaround?
>
> It would be really great if someone from google could weigh in here.
> Thanks!
>
> --
> 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 
> athttp://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] GAE's http header length limit, bug or undocumented restriction?

[Brandon Wirtz]

400 is the specification limit for http header elements.
(actually I think it is 400 characters converted to Base64)

Most things don't break if you go over this,

The max size for all Http Headers is 4k


-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of tempy
Sent: Monday, January 16, 2012 10:40 AM
To: Google App Engine
Subject: [google-appengine] GAE's http header length limit, bug or
undocumented restriction?

Hi All,

I've hit a behavior that doesn't exist on the dev-server, which is that
custom http headers on the response seem to be limited to around
400 characters. One custom header that I'm using which is regularly about
700 chars is simply silently dropped from the response.

Firstly - this restriction, if its not a bug, should be documented.
I've spent a whole lot of time building a feature around a big http header
which worked fine all along on the dev server, if I have to re- architect
this feature then it'll be a few days of work down the tubes.

Secondly - is this a bug? This issue:
http://code.google.com/p/googleappengine/issues/detail?id=407
Seems to indicate that this is a bug, but its marked as fixed and it is
clearly not fixed. If it is a bug, is there a known workaround?

It would be really great if someone from google could weigh in here.
Thanks!

--
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] Error in some instances

[LSH]

Hi,

I am getting this error in a GAE/Py app


   1. 
   
   ms=2116 cpu_ms=5152 api_cpu_ms=3612 cpm_usd=0.143288 
instance=00c61b117c9067bd7cc893963797b9a4bbb358
   
   2.  E 2012-01-16 20:24:10.269  
   
   Traceback (most recent call last):
   
   3.  E 2012-01-16 20:24:10.269  
   
 File "/base/python_runtime/python_dist/lib/python2.5/wsgiref/handlers.py", 
line 92, in run
   
   4.  E 2012-01-16 20:24:10.269  
   
   self.result = application(self.environ, self.start_response)
   
   5.  E 2012-01-16 20:24:10.269  
   
 File 
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/_webapp25.py",
 line 722, in __call__
   
   6.  E 2012-01-16 20:24:10.269  
   
   response.wsgi_write(start_response)
   
   7.  E 2012-01-16 20:24:10.269  
   
 File 
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/_webapp25.py",
 line 330, in wsgi_write
   
   8.  E 2012-01-16 20:24:10.269  
   
   write = start_response('%d %s' % self.__status, self.__wsgi_headers)
   
   9.  E 2012-01-16 20:24:10.269  
   
 File "/base/python_runtime/python_dist/lib/python2.5/wsgiref/handlers.py", 
line 185, in start_response
   
   10.  E 2012-01-16 20:24:10.269  
   
   assert type(val) is StringType,"Header values must be strings"
   
   11.  E 2012-01-16 20:24:10.269  
   
   AssertionError: Header values must be strings
   
   
As you can see, none of my app's code has been launched yet, so it is not 
related with my coding. Surprisingly, the same request does work sometimes, 
depending on the instances where it is being launched.

-- 
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/-/YM082qxZ_FIJ.
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] Persistence Error

[Victor Perticarrari]

It was a concurrency error.

Thanks!

2012/1/15 Amy Unruh 

> Victor,
>
> Your example is a bit abstract, but a general test (e.g., see this code
> snippet - http://pastebin.com/u6RHWqe6 ) works fine.  You might double
> check that your instances do have the intended content prior to persisting
> them.
>
>
> On Sat, Jan 14, 2012 at 8:46 AM, Victor Emanuel <
> victor.perticarr...@gmail.com> wrote:
>
>> I have a class:
>>
>>@PersistenceCapable
>>public class X{
>>@Persistent
>>@Order(extensions = @Extension(vendorName = "datanucleus", key
>> = "list-ordering", value = "date desc"))
>>private List list;
>>
>>@Persistent
>>private Float value;
>>}
>>
>> When I try to make:
>>
>>PersistenceManager pm = PMF.get().getPersistenceManager();
>>try {
>>X x = pm.getObjectById(X.class, id);
>>x.setValue(listObject.getValue().floatValue());
>>x.getList().add(listObject);
>>} finally {
>>pm.close();
>>}
>>
>> I'm expecting that in my X object I will add a listValue and set the
>> value of 'value'. But the result is only adding the value in the list,
>> ignoring the setting of ghe value!
>>
>> Is there anything wrong?
>>
>> --
>> 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.
>



-- 
Victor Emanuel
"God gave rock and roll to you
Put it in the soul of everyone"

-- 
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: Unable to get dynamic backend to start on receiving browser request

[Johan Euphrosine]

What is your application id ?

On Mon, Jan 16, 2012 at 2:17 PM, jon  wrote:

> Upgrated to GAE/J 1.6.1.1. Still no luck. Anybody?
>
> On Jan 16, 5:13 pm, jon  wrote:
> > Hi,
> >
> > I've read and re-read the documentation and have tried various things
> > but I haven't been able to get dynamic backend to start automatically
> > on receiving user request.
> >
> > Here's my config:
> >
> > 
> >   
> > B2
> > 1
> > 
> >   true
> >   true
> > 
> >   
> > 
> >
> > When I hit backenda.myapp.appspot.com I always get a 503 error with
> > the following error message:
> >
> > Error: Server Error
> >
> > The service you requested is not available yet.
> > Please try again in 30 seconds.
> >
> > 
> >
> > Am I missing something? I'm still on GAE/J 1.5.5.
>
> --
> 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.
>
>


-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
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] GAE's http header length limit, bug or undocumented restriction?

[tempy]

Hi All,

I've hit a behavior that doesn't exist on the dev-server, which is
that custom http headers on the response seem to be limited to around
400 characters. One custom header that I'm using which is regularly
about 700 chars is simply silently dropped from the response.

Firstly - this restriction, if its not a bug, should be documented.
I've spent a whole lot of time building a feature around a big http
header which worked fine all along on the dev server, if I have to re-
architect this feature then it'll be a few days of work down the
tubes.

Secondly - is this a bug? This issue:
http://code.google.com/p/googleappengine/issues/detail?id=407
Seems to indicate that this is a bug, but its marked as fixed and it
is clearly not fixed. If it is a bug, is there a known workaround?

It would be really great if someone from google could weigh in here.
Thanks!

-- 
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Brandon Wirtz]

I agree multiple imports is not supposed to be a problem, but I have seen it
cause issues, or seen issues be resolved by not doing it.
 
Remember that the Google Implementation of Python has its own "Specialness"
and what is true in traditional python is not always quite the same in GAE
land.
 
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Karl Rosaen
Sent: Monday, January 16, 2012 7:32 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Why are several production issues
related to DeadlineExceededErrors being ignored?
 
Brandon, thanks so much for taking the time to put together the video, very
helpful.
 
The key insight seem to be: time spent in the queue waiting for a frontend
counts towards the limit for a DeadlineExceedError.  This seems silly -
seems to me user visible latency, and framework level timeout enforcement
should be decoupled in this case.  But good insight and glad to better
understand this behavior.  This also makes me wonder what the benefit of
having 'auto' for max pending latency would ever be - I'm going to slide
mine down to ~1s.
 
One quibble about your advice for 'avoid importing code more than once':
this shouldn't be a major issue in python unless you are importing a module
from within a function that is called several times:
 
Although Python's interpreter is optimized to not import the same module
multiple times, repeatedly executing an import statement can seriously
affect performance in some circumstances.
 
http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Import_Statement_Ove
rhead
 
Just wanted to clarify that one needn't fret about the same utility module
being imported from two modules or anything like that.
 
Karl
-- 
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/-/7FTyQ34tagsJ.
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] Not able to deploy application with GAE 1.6.1

[Deepak Singh]

Hi All,

I recently upgraded to GAE 1.6.1.

When i deploy my app through Eclipse deploy option, it gives me Invalid
OATH exception.

And when i do rollback through command prompt, it gives me the following
exception

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
version n
umber in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)

And, when i do the rollback using GAE 1.5.5 which i was using earlier, it
does fine.

Can some one has any idea about it?

Also, Does it make any difference to the production if i deploy my app
using 1.5.5 instead of 1.6.1 as i believe that production server must be
using the latest version of GAE?

Thanks
Deepak

-- 
Deepak Singh

-- 
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] Not able to deploy application with 1.6.1

[Deepak Singh]

Hi All,

I recently upgraded to GAE 1.6.1.

When i deploy my app through Eclipse deploy option, it gives me Invalid
OATH exception.

And when i do rollback through command prompt, it gives me the following
exception

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
version n
umber in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)

And, when i do the rollback using GAE 1.5.5 which i was using earlier, it
does fine.

Can some one has any idea about it?

Also, Does it make any difference to the production if i deploy my app
using 1.5.5 instead of 1.6.1 as i believe that production server must be
using the latest version of GAE?

Thanks
Deepak

-- 
Deepak Singh

-- 
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Karl Rosaen]

Kenneth, 

Agreed that running on the master / slave datastore is a liability these 
days (which IMO is pretty irresponsible on GAEs part, I see no reason why 
major latency spikes can't be avoided even if there are advantages to the 
high replication datastore and we can eventually migrate. If we must 
migrate, give us a deadline, and fully support the master/slave until then. 
 but I digress...) but the DEEs we're talking about here are happening 
during warmup unrelated to datastore operations, and could effect anyone 
regardless of master/slave vs HR.  For these cases I think Brandon's advice 
is spot on: lower your max pending latency to 1s or so.

Usually when we get hit with DEEs related to being on master / slave, I can 
see a corresponding spike in the system status dashboard:

http://code.google.com/status/appengine/detail/datastore/2012/01/16#ae-trust-detail-datastore-get-latency

and at least I know what's going on.  Actually, despite my whining, the 
last time we were hit by DEEs related to master/slave datastore latency 
spikes was over a month ago - GAE folks if you are listening and you have 
been trying to improve the reliability of master / slave, thank you.  I 
think when we were getting pounded by DEEs last week I started to freak out 
and pointed the finger at master / slave latency prematurely when it was 
really related to DEEs during warmup.

Anyways, thanks to Brandon, I also know what's going on in the case of DEEs 
during warmup too!

Best,
Karl

-- 
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/-/vpGUvTpkovgJ.
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Karl Rosaen]

Brandon, thanks so much for taking the time to put together the video, very 
helpful.

The key insight seem to be: time spent in the queue waiting for a frontend 
counts towards the limit for a DeadlineExceedError.  This seems silly - 
seems to me user visible latency, and framework level timeout enforcement 
should be decoupled in this case.  But good insight and glad to better 
understand this behavior.  This also makes me wonder what the benefit of 
having 'auto' for max pending latency would ever be - I'm going to slide 
mine down to ~1s.

One quibble about your advice for 'avoid importing code more than once': 
this shouldn't be a major issue in python unless you are importing a module 
from within a function that is called several times:

Although Python's interpreter is optimized to not import the same module 
> multiple times, repeatedly executing an import statement can seriously 
> affect performance in some circumstances.


http://wiki.python.org/moin/PythonSpeed/PerformanceTips#Import_Statement_Overhead

Just wanted to clarify that one needn't fret about the same utility module 
being imported from two modules or anything like that.

Karl

-- 
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/-/7FTyQ34tagsJ.
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Kenneth]

Are we talking master slave or high replication datastores?  If we're 
talking master slave, and I'm pretty certain we are, then forget it. 
 Google isn't going to help you.  You need to migrate to hrd to avoid these 
problems.  My life was hell with deadline errors.  Then I bit the bullet 
and migrated and not a single timeout error since.

If you are on hrd then I'm at a loss.

-- 
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/-/9CIJs6DwoUwJ.
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: Unable to get dynamic backend to start on receiving browser request

[jon]

Upgrated to GAE/J 1.6.1.1. Still no luck. Anybody?

On Jan 16, 5:13 pm, jon  wrote:
> Hi,
>
> I've read and re-read the documentation and have tried various things
> but I haven't been able to get dynamic backend to start automatically
> on receiving user request.
>
> Here's my config:
>
> 
>   
>     B2
>     1
>     
>       true
>       true
>     
>   
> 
>
> When I hit backenda.myapp.appspot.com I always get a 503 error with
> the following error message:
>
> Error: Server Error
>
> The service you requested is not available yet.
> Please try again in 30 seconds.
>
> 
>
> Am I missing something? I'm still on GAE/J 1.5.5.

-- 
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Brandon Wirtz]

We may have to get someone from GOOG to weigh in.

Requests have a 60s time limit, but from testing it seems that
Initialization has a 15s limit.  I don't know if this is a bug, a feature,
or a flaw in my testing.

Also my "best practices" doesn't guarantee to fix everything, there could
still be a bug, but I was hoping that be eliminating the obvious causes we
might get closer to resolution.



-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Alexis
Sent: Monday, January 16, 2012 1:30 AM
To: Google App Engine
Subject: [google-appengine] Re: Why are several production issues related to
DeadlineExceededErrors being ignored?

Thanks for the shot!

Here are some comments:

- isn't the limit 60sec instead of 15sec?

- We indeed have the pending latency slider set to default, but out of our
12 instances we have 3 resident ones, so the slider will have little effect
on our application's performance.

- Requests that DEE typically have this signature:
ms=63498 cpu_ms=1097 api_cpu_ms=0 cpm_usd=0.030639 loading_request=1
pending_ms=373 exit_code=104
So it did not spent much time waiting to be served... And the DEE is raised
during the import phase.

- Our warmup requests, that import most of our modules then return a simple
"ok" string, take in average 2100ms to complete (min 860, max 3800).
But during DEE spikes they can also raise DEE.

--
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: Time lag with logging

[Sagi]

Happens to me as well and makes it really hard to see what's going on
when troubleshooting issues.


On Dec 7 2011, 2:55 am, Jane Abernethy 
wrote:
> Hi,
>
> I am noticing a bit of a time lag with logging - I'll log something, call
> the method and the logs wont update for about 15 minutes. Is anyone else
> experiencing this?

-- 
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: Why are several production issues related to DeadlineExceededErrors being ignored?

[Alexis]

Thanks for the shot!

Here are some comments:

- isn't the limit 60sec instead of 15sec?

- We indeed have the pending latency slider set to default,
but out of our 12 instances we have 3 resident ones, so the slider
will have little effect on our application's performance.

- Requests that DEE typically have this signature:
ms=63498 cpu_ms=1097 api_cpu_ms=0 cpm_usd=0.030639 loading_request=1
pending_ms=373 exit_code=104
So it did not spent much time waiting to be served... And the DEE is
raised during the import phase.

- Our warmup requests, that import most of our modules then return a
simple "ok" string, take in average 2100ms to complete (min 860, max
3800).
But during DEE spikes they can also raise DEE.

-- 
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.