Re: [google-appengine] Re: Completely removing an application

2018-05-31 Thread Hamish Wadham
Totally agree. I too am looking at alternatives to AWS which we currently use. If you don't need something it needs to be removable. I too am cautious of some costs sneaking in. On Tuesday, December 15, 2015 at 6:23:39 AM UTC+13, Mark Betz wrote: > > Christian, it's probably a lack of trust on my

[google-appengine] Re: App Engine blocking users due to Unusual Traffic

2013-04-10 Thread Hamish
gt;. So not terribly helpful. Cheers, Hamish On Tuesday, 9 April 2013 17:58:15 UTC+1, Vinny P wrote: > > Whoa, you asked a lot of questions there! Taking it question by question: > > > On Monday, April 8, 2013 3:37:42 AM UTC-5, Hamish wrote: >> >> We are gett

[google-appengine] Re: App Engine blocking users due to Unusual Traffic

2013-04-08 Thread Hamish
Also - I'm not sure why this happened but the visibility of the production ticket I created was changed to "Only users with Commit permission can see this issue." last week for some reason. On Monday, April 8, 2013 9:37:42 AM UTC+1, Hamish wrote: > > We are getting rep

[google-appengine] App Engine blocking users due to Unusual Traffic

2013-04-08 Thread Hamish
We are getting reports from some of our users that they are getting blocked from making requests to our application on App Engine. They say they are getting the following message: "Our systems have detected unusual traffic from your computer network. Please try your request again later." Thi

Re: [google-appengine] Service Failure - all instances restarted simultaneously

2012-06-07 Thread Hamish
geographic spread to the location of instances if requests are coming in from different parts of the world. Thanks again you for your help, Hamish On Tuesday, June 5, 2012 1:37:26 PM UTC+1, Takashi Matsuo (Google) wrote: > > > Hi Hamish, > > It's totally an expected behav

[google-appengine] Service Failure - all instances restarted simultaneously

2012-06-05 Thread Hamish
id is dacloudapi. Why would this happen? It seems very odd for "all" instances including the resident to restart at the same time. Can someone please look into this for me? Thank you, Hamish -- You received this message because you are subscribed to the Google Groups "Google Ap

Re: [google-appengine] Lots of HTTP 500 errors and all instances restarted by GAE!

2012-03-13 Thread Hamish
Hi, I will email the app id rather than post it on this public forum. We are still seeing HTTP 500 errors today. Instances seem to take a long time to come up. We are using HR datastore. Tanks, Hamish On Friday, March 9, 2012 7:00:57 PM UTC, Takashi Matsuo (Google) wrote: > > >

[google-appengine] Lots of HTTP 500 errors and all instances restarted by GAE!

2012-03-08 Thread Hamish
is very serious and we need to get to the bottom of it. Thanks, Hamish -- 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/-/E2c_GofputsJ.

[google-appengine] Request log format, can it be changed?

2011-06-22 Thread Hamish
Hi, Is it possible to change the request log format used in GAE? I want to capture additional HTTP headers. I could use the app logging and write them out to INFO but I'd prefer not to. Cheers -- You received this message because you are subscribed to the Google Groups "Google App Engine" grou

[google-appengine] Re: App response times very poor with high pending_ms time

2011-06-22 Thread Hamish
ther > option is to 'prime' the app with a couple smaller bursts of traffic > to get a few instances spun up. > > Robert > > On Thu, May 26, 2011 at 07:36, Hamish wrote: > > Hi, > > > We are developing a Java app for Google App Engine. We did some > > te

[google-appengine] App response times very poor with high pending_ms time

2011-05-26 Thread Hamish
Hi, We are developing a Java app for Google App Engine. We did some testing today using "ab" to hit a particular URL. We had 1000 concurrent threads in ab hitting the URL 1 million times. We were surprised by the response times. A lot of the responses were taking well over a second to return with