Is anyone else experiencing this? My app ID is chesspresso-service and
since the early hours of this morning it's been hitting these over and over
again..
1.
1. 2013-09-15 09:15:08.976
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppCon
Hello,
I noticed that appstats do not display the data for the calls originating
from servlet filters.
Is this true, or should I enable any settings to see the data from the
servlet filters.
-Aswath
--
You received this message because you are subscribed to the Google Groups
"Google App Engine"
I do some performance stuff, but that will save me only 200-300ms. Other
that that, no special code is in the servlets.
Following are debug logs that take 4038ms and 235ms for the same request.
Please find the code that happens between "LoginFilter Begin" and "before
chain.doFilter()".
In the be
Becuase time is money and in April 2015 I might be able to just retire the
app instead of doing the work.
I'm busy you know!
On Sunday, 15 September 2013 06:32:57 UTC+10, barryhunter wrote:
>
> Why wait? Update now. Just do it. Don't waste time thinking if you should
> be updating, when you co
Why wait? Update now. Just do it. Don't waste time thinking if you should
be updating, when you could actully be using that time updating!
Why run the risk that it could be turned off at any time with little
warning. (although I expect they will always try to give some warning)
In theory the dep
How long do I have before I have to update my new app to python 2.7 and the
new db? Is there a specified date when my old app will no longer function?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop
Im trying to find the right way to organize my webapp2 application. This is
the file structure:
/my-app
app.yaml
main.app
/views
index.html
/handlers
__init__.py
base.py
home.py
handlers/base.py
import webapp2from webapp2_extras import jinja2
class
On Saturday, September 14, 2013 2:57:35 PM UTC+8, aswath wrote:
>
> If a request a served by an instance that is alive for sometime, then it
> is fine.
> However, sometimes the request is directed to a new instance. Any first
> request for a new instance is adding a considerable delay.
>
>
This
