[google-appengine] Re: GAE access is pretty slow/times out...

It is just not the dashboard...I am seeing sporadic data store timeouts.. On Mon, Jan 24, 2011 at 2:44 PM, Kangesh Gunaseelan wrote: > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send

[google-appengine] GAE dashboard access is pretty slow/times out...

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

Re: [google-appengine] Re: Requests are timing out and GAE is slow...

I am. I am not seeing that issue though - tasks are running properly and admin page is loading fine. On Wed, Jan 5, 2011 at 1:40 PM, Chris Vaughn wrote: > Are any of you guys using Task Queues? > > It seems that some of my Tasks aren't running but the Task Queues admin > page is giving me a 500

Re: [google-appengine] Re: Requests are timing out and GAE is slow...

Seems to be back up now for me as well.. On Wed, Jan 5, 2011 at 1:31 PM, john wrote: > And yep, my pages seem to have returned also. > > > On Jan 5, 4:29 pm, john wrote: > > Both my apps are down too. > > > > Actually, one of my apps has static files and they still seem to be > > serving. The

[google-appengine] Requests are timing out and GAE is slow...

I am seeing requests failing for the past few minutes or so... Are others experiencing any issue with GAE at the moment? Thanks, Kangesh -- 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-appeng...@

Re: [google-appengine] Re: Prerelease SDK 1.4.0 is out!

Awesome additions. Are you able to share the pricing terms for Always On feature now? Thanks! On Thu, Nov 18, 2010 at 3:17 PM, Ikai Lan (Google) > wrote: > Always On will be a paid feature you enable in the admin console. > > I'll post some light sample code for channel API and warmup requests

Re: [google-appengine] Re: Can't get into dashboard?

Same here. On Sat, Nov 6, 2010 at 9:28 AM, Jeremy Benetz wrote: > Same here. It's the App Engine. > > -- > 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-appeng...@googlegroups.com. > To unsubs

Re: [google-appengine] Re: Unable to Access Dashboard or Logs

This issue happening again now. On Tue, Nov 2, 2010 at 9:28 PM, Krishna wrote: > I'm unable to access the admin console. The login page @ > appengine.google.com, well, returns me to the login page. > > > > On Nov 2, 8:57 pm, "Sean Lynch (Google)" wrote: > > Admin Console accessibility issues

Re: [google-appengine] Unable to Access Dashboard or Logs

Same here. Is there any update on resolving the latency issues? I love the capabilities of what Google app engine offers and they are very powerful but I do have to say unless the stability issues are addressed (and we do see these latency issues more often), these capabilities are good for a pro

[google-appengine] Is App Engine Ok now for others? Too many errors in 8:21 AM

Hello, I am getting a bunch of HardDeadlineExceededError this morning and Request Aborted errors since 8:20 AM PST today. None of the requests in the past 20 minutes have succeeded. Are others experiencing the issue? Google folks, Can you please update? Thanks! -- You received this message be

Re: [google-appengine] Re: Latency related follow up

nces to reduce application loading overhead". > > > On Oct 5, 12:47 pm, Kangesh Gunaseelan wrote: > > Thanks for your suggestion. > > > > I will take a look at the appstats one more time. What I am noticing > though > > is api_cpu under 500ms (and many much b

[google-appengine] Re: Requesting help with appstats

like beta instance to be fixed. Google support team - my beta app name is chitterbeta. Thanks much! On Tue, Oct 5, 2010 at 2:12 PM, Kangesh Gunaseelan wrote: > I updated > > > > > > > > but I am still seeing error. Error logs have this warning: > > >

[google-appengine] Re: Requesting help with appstats

! On Tue, Oct 5, 2010 at 11:35 AM, Kangesh Gunaseelan wrote: > I am stumped on this issue for some reason.. > I have vanilla appstats configuration to web.xml and deployed properly but > the request to appname.appspot.com/appstats/ reports a server error: > Error: Server ErrorThe server

[google-appengine] Requesting help with appstats

I am stumped on this issue for some reason.. I have vanilla appstats configuration to web.xml and deployed properly but the request to appname.appspot.com/appstats/ reports a server error: Error: Server ErrorThe server encountered an error and could not complete your request. If the problem persis

[google-appengine] App Engine console is down!

Are folks experiencing this issue? Thanks. Error: Server ErrorThe server encountered an error and could not complete your request. If the problem persists, please report your problem and mention this error message and the query that caused it. --

Re: [google-appengine] Re: Latency related follow up

Thanks for your suggestion. I will take a look at the appstats one more time. What I am noticing though is api_cpu under 500ms (and many much below that) but sometimes overall cpu overshoots 700 ms. More over, for request aborted error messages, it doesn't really look like the service is even call

Re: [google-appengine] Re: Latency related follow up

Hi, Thanks for your feedback. That is good to know. I think I am handling errors reasonably well but there is only so much an app developer can do to handle the errors. Ultimately, it is the end user that will need to resolve the error. Here is an example: When an end user tries to post a messa

Re: [google-appengine] Re: 30 to 40% requests failing due to latency issues?

Unfortunately for me, I launched the service couple of days ago, sent out promotional email and customers are experiencing slow downs and errors. Hope this issue is getting a very high priority attention at Google and a permanent resolution is targeted for the very near future (hopefully, hours).