I'm seeing the same, unrelated to indexes or any changes. I was deploying a 
version of the app with only a logging change and I see 121 on new 
deployments/versions.

On Tuesday, May 8, 2012 11:51:11 AM UTC-5, Stu Thorne wrote:
>
> Hi, 
>
> I have been seeing similar issues today. I believe they are of my own 
> doing, and here are my steps to resolution in case they help: 
>
> Issue 
>
> * I had manually edited the index.yaml file for Datastore indexes, and 
> had not cleaned up the indexes in the dev server 
> * This caused the same, intermittent error responses and log messaging 
> that you have been seeing, on all HTTP Requests 
>
> Resolution 
>
> * Rolled back index.yaml from source control file and redeployed 
> * No further issues present with current testing 
>
> Hope this helps. 
>
> Stu 
>
>
> On May 8, 1:35 pm, maek75 <martin.ekst...@apegroup.com> wrote: 
> > Hi, we have an app running on GAE, developed with java/spring. The app 
> > has been running fine until today, when we suddenly see lots of error 
> > messages in the logs (see below). What do they mean? The app performs 
> > openId authentication based on openid4java. We don't use own threads 
> > and as said, the app worked fine earlier. Could it be that we today 
> > face much more requests and the fact that opened needs to redirect the 
> > user back and forth? Even requesting a simple resource (like below) 
> > gives the same error. Note that the error doesn't occur for every 
> > request. 
> > 
> >     @RequestMapping(value = "/auth/openid/success", produces = "text/ 
> > html") 
> >     public String loadSuccessPage(HttpServletResponse 
> > httpServletResponse, Model uiModel) { 
> >         return "auth/openid/success"; 
> >     } 
> > 
> > ERRORS FOUND IN ERROR LOG (we got below errors in same request): 
> > 
> > I 2012-05-08 05:26:29.638 
> > 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 request may thus take longer and use more CPU than a typical 
> > request for your application. 
> > 
> > W 2012-05-08 05:26:29.638 
> > 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) 
> > 
> > ... and on the web page: 
> > Error: Server Error 
> > 
> > The 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.

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

Reply via email to