[google-appengine] Re: Instances trying to start and failing.

2013-06-26 Thread Bart Jenkins

I'm having the same problems. GAE is non-functional for me right now.

On Tuesday, June 25, 2013 7:06:49 AM UTC-4, aswath wrote:

 Hello Appengine Team,
 http://accountingguru-india.appspot.com customers are facing the latency 
 issues, and are not able to login to the application.

 Logs show the following

 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. (Error code 121


1. 
   1. 2013-06-25 16:18:41.749 /tenantmgr/listTenant 500 14192ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. W2013-06-25 16:18:41.749 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 
2. 
   1. 2013-06-25 16:18:07.028 /tenantmgr/listTenant 500 33426ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. I2013-06-25 16:18:06.584 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 
   3. W2013-06-25 16:18:06.584 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 
3. 
   1. 2013-06-25 16:17:35.852 /tenantmgr/listTenant 500 41223ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. W2013-06-25 16:17:35.852 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 
4. 
   1. 2013-06-25 16:17:26.627 /tenantmgr/listTenant 500 52491ms 0kb 
 Mozilla/5.0 
   (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) 
   Chrome/27.0.1453.116 Safari/537.36 
   2. I2013-06-25 16:17:26.562 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 
   3. W2013-06-25 16:17:26.562 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 



 A production issue is also submitted.
 https://code.google.com/p/googleappengine/issues/detail?id=9569.

 Any other appid facing similar issue?


 Regards
 -Aswath
 www.acccounting-guru.net





-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.




[google-appengine] Re: Instances trying to start and failing.

2013-06-26 Thread Egolike
We are experiencing this same issue right now, every petition sent to the 
server hosted in appengine is being thrown back with that error.

Could anyone explain why this happens? We have been working fine until 
yesterday...

On Tuesday, June 25, 2013 1:06:49 PM UTC+2, aswath wrote:

 Hello Appengine Team,
 http://accountingguru-india.appspot.com customers are facing the latency 
 issues, and are not able to login to the application.

 Logs show the following

 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. (Error code 121


1. 
   1. 2013-06-25 16:18:41.749 /tenantmgr/listTenant 500 14192ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. W2013-06-25 16:18:41.749 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 
2. 
   1. 2013-06-25 16:18:07.028 /tenantmgr/listTenant 500 33426ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. I2013-06-25 16:18:06.584 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 
   3. W2013-06-25 16:18:06.584 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 
3. 
   1. 2013-06-25 16:17:35.852 /tenantmgr/listTenant 500 41223ms 0kb 
 Mozilla/4.0 
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR 
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) 
   2. W2013-06-25 16:17:35.852 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 
4. 
   1. 2013-06-25 16:17:26.627 /tenantmgr/listTenant 500 52491ms 0kb 
 Mozilla/5.0 
   (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) 
   Chrome/27.0.1453.116 Safari/537.36 
   2. I2013-06-25 16:17:26.562 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 
   3. W2013-06-25 16:17:26.562 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 



 A production issue is also submitted.
 https://code.google.com/p/googleappengine/issues/detail?id=9569.

 Any other appid facing similar issue?


 Regards
 -Aswath
 www.acccounting-guru.net





-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [google-appengine] Re: Instances trying to start and failing.

2013-06-26 Thread Vinny P
+1, Also seeing multiple instance restarts and instance recycling taking
place on my end.


-
-Vinny P
Technology  Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com




On Wed, Jun 26, 2013 at 3:31 AM, Egolike sys...@egolike.com wrote:

 We are experiencing this same issue right now, every sent to the server
 hosted in appengine is being thrown back with that error.

 Could anyone explain why this happens? We have been working fine until
 yesterday...


 On Tuesday, June 25, 2013 1:06:49 PM UTC+2, aswath wrote:

 Hello Appengine Team,
 http://accountingguru-india.**appspot.comhttp://accountingguru-india.appspot.comcustomers
  are facing the latency issues, and are not able to login to the
 application.

 Logs show the following

 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. (Error code 121


1.
   1. 2013-06-25 16:18:41.749 /tenantmgr/**listTenant 500 14192ms 0kb
   Moz**illa/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64;
   Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
   3.0.30729; Media Center PC 6.0)
   2. W2013-06-25 16:18:41.749 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
2.
   1. 2013-06-25 16:18:07.028 /tenantmgr/**listTenant 500 33426ms 0kb
   Moz**illa/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64;
   Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
   3.0.30729; Media Center PC 6.0)
   2. I2013-06-25 16:18:06.584 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
   3. W2013-06-25 16:18:06.584 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
3.
   1. 2013-06-25 16:17:35.852 /tenantmgr/**listTenant 500 41223ms 0kb
   Moz**illa/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64;
   Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
   3.0.30729; Media Center PC 6.0)
   2. W2013-06-25 16:17:35.852 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
4.
   1. 2013-06-25 16:17:26.627 /tenantmgr/**listTenant 500 52491ms 0kb
   Moz**illa/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like
   Gecko) Chrome/27.0.1453.116 Safari/537.36
   2. I2013-06-25 16:17:26.562 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
   3. W2013-06-25 16:17:26.562 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



 A production issue is also submitted.
 https://code.google.com/p/**googleappengine/issues/detail?**id=9569https://code.google.com/p/googleappengine/issues/detail?id=9569
 .

 Any other appid facing similar issue?


 Regards
 -Aswath
 www.acccounting-guru.net



  --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-appengine+unsubscr...@googlegroups.com.
 To post to this group, send email to google-appengine@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.




[google-appengine] Re: Instances trying to start and failing.

2013-06-25 Thread Aswath Satrasala
 Datastore Errors:

2013-06-25 16:55:32.342

http://www.accounting-guru.net/tenantmgr/listTenant
javax.servlet.ServletException:
com.google.appengine.api.datastore.DatastoreFailureException: internal
error.
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:268)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at 
com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:146)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:439)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:483)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:490)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:777)
at 
com.google.tracing.TraceContext$DoInTraceContext.runInContext(TraceContext.java:754)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:345)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:337)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:487)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.google.appengine.api.datastore.DatastoreFailureException:
internal error.
at 
com.google.appengine.api.datastore.DatastoreApiHelper.translateError(DatastoreApiHelper.java:53)
at 
com.google.appengine.api.datastore.DatastoreApiHelper$1.convertException(DatastoreApiHelper.java:76)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:106)
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.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$1.runInternal(DatastoreServiceImpl.java:78)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl$1.runInternal(DatastoreServiceImpl.java:75)
at 
com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:31)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:75)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:62)
at 
com.google.apphosting.runtime.jetty.DatastoreSessionStore.getSession(DatastoreSessionStore.java:82)
at 
com.google.apphosting.runtime.jetty.SessionManager.loadSession(SessionManager.java:327)
at 
com.google.apphosting.runtime.jetty.SessionManager.getSession(SessionManager.java:301)
at 
org.mortbay.jetty.servlet.AbstractSessionManager.getHttpSession(AbstractSessionManager.java:237)
at 
org.mortbay.jetty.servlet.SessionHandler.setRequestedId(SessionHandler.java:246)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:136)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:266)


On Tue, Jun 25, 2013 at 4:36 PM, Aswath Satrasala 
aswath.satras...@gmail.com wrote:

 Hello Appengine Team,
 http://accountingguru-india.appspot.com customers are facing the latency
 issues, and are not able to login to the application.

 Logs show the following

 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. (Error code 121


1.
   1. 2013-06-25 16:18:41.749 /tenantmgr/listTenant 500 14192ms 0kb 
 Mozilla/4.0
   (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET 
 CLR
   2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
   2. W2013-06-25 16:18:41.749 A problem was encountered with the
   process that handled this