[appengine-java] java.lang.IllegalStateException: Committed
I have a warning "java.lang.IllegalStateException: Committed" when I deploy to GAE. I test it at local, and it's can work. But it's not work at GAE I see the logs java.lang.IllegalStateException: Committed at org.mortbay.jetty.Response.resetBuffer(Response.java:1024) at org.mortbay.jetty.Response.sendRedirect(Response.java:428) at org.apache.jsp.areaair_jsp._jspService(areaair_jsp.java:112) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java: 102) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java: 35) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java: 43) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 182) 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: 249) 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: 135) at com.google.apphosting.runtime.JavaRuntime $RequestRunnable.run(JavaRuntime.java:422) at com.google.tracing.TraceContext $TraceContextRunnable.runInContext(TraceContext.java:449) at com.google.tracing.TraceContext$TraceContextRunnable $1.run(TraceContext.java:455) at com.google.tracing.TraceContext.runInContext(TraceContext.java: 695) at com.google.tracing.TraceContext $AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java: 333) at com.google.tracing.TraceContext $AbstractTraceContextCallback.runInInheritedContext(TraceContext.java: 325) at com.google.tracing.TraceContext $TraceContextRunnable.run(TraceContext.java:453) at com.google.apphosting.runtime.ThreadGroupPool $PoolEntry.run(ThreadGroupPool.java:251) at java.lang.Thread.run(Thread.java:679) I don't know why? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Can't initiate backend instance
Well.. I found where is the problem. Doing many deploys as declarations in *web.xml*, I could identify (* step-by-step*) which configuration was breaking the backend instance startup. I could certainly, for sure, isolate this declaration: > Faces Servlet > **.html* > Experimenting changing **.html*, to **.jsf* *and, *later to **.xhtml* resolved the problem. Changing back to **.html* broke it again. I would guess something related to the startup request path (_ah/start/), but I can't assert nothing. I hope it help someone.. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/AH4kg867LDoJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Can't initiate backend instance
Disabling all filters (Apache Shiro, AppStats, Jersey, Primefaces) and JSF servlets, make it works. Now i'm trying to identify what is breaking the instance.. Anyone know issues related with these frameworks/apps? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/usIqtEgwaqgJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Can't initiate backend instance
Hi guys, I don't know what to do anymore. I can't start my backend instance, it always the same message. Front-end instances works correctly but backend... I'm using JSF, Jersey for REST web services. Process terminated because it failed to respond to the start request with an HTTP status code of 200-299 or 404. I've already googled a lot, but no answers... 1. 2012-01-15 22:52:24.347 /_ah/start 302 14447ms 0kb instance=0 0.1.0.3 - - [15/Jan/2012:16:52:24 -0800] "GET /_ah/start HTTP/1.1" 302 80 - - "0.dbload.zurbb-beta.appspot.com" ms=14447 cpu_ms=10663 api_cpu_ms=0 cpm_usd=0.27 loading_request=1 exit_code=111 instance=0 2. I2012-01-15 22:52:13.752 com.sun.faces.config.ConfigureListener contextInitialized: Initializing Mojarra 2.0.4 (FCS b09) for context '' 3. I2012-01-15 22:52:17.057 com.sun.faces.spi.InjectionProviderFactory createInstance: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed. 4. I2012-01-15 22:52:18.376 com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp: JSF1027: [null] The ELResolvers for JSF were not registered with the JSP container. 5. I2012-01-15 22:52:19.498 com.sun.jersey.api.core.PackagesResourceConfig init: Scanning for root resource and provider classes in the packages: com.zurbb.ws 6. I2012-01-15 22:52:19.598 com.sun.jersey.api.core.ScanningResourceConfig logClasses: Root resource classes found: class com.zurbb.ws.HubResources 7. I2012-01-15 22:52:19.598 com.sun.jersey.api.core.ScanningResourceConfig init: No provider classes found. 8. I2012-01-15 22:52:19.772 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17 PM' 9. I2012-01-15 22:52:22.856 com.sun.jersey.api.core.PackagesResourceConfig init: Scanning for root resource and provider classes in the packages: com.zurbb.internal 10. I2012-01-15 22:52:22.876 com.sun.jersey.api.core.ScanningResourceConfig logClasses: Root resource classes found: class com.zurbb.internal.InternalResources 11. I2012-01-15 22:52:22.877 com.sun.jersey.api.core.ScanningResourceConfig init: No provider classes found. 12. I2012-01-15 22:52:22.878 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17 PM' 13. I2012-01-15 22:52:24.339 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. 14. E2012-01-15 22:52:24.339 Process terminated because it failed to respond to the start request with an HTTP status code of 200-299 or 404. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/SHCBpqSZ-YwJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: is there any solution/idea how blacklist IP in "realtime" ?
Using a programmatic aproach can't save your "Incoming Bandwidth" quota. I created a feature request for rate limiting here; http://code.google.com/p/googleappengine/issues/detail?id=6733 Don't forget to star it. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/zEejZHcFJ5sJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Java app-engine bug is bad news for upcoming http://opencfsummit.org/
The code in the link works just fine for me, both running SDK 1.6.1 and 1.5.3 http://groups.google.com/group/google-appengine/browse_thread/thread/11749e1254bcd165/46cd9826877b46c9 Could you tell us a bit more about your design, are you using Servlet Filters? Best regards Dick Larsson www.amantech.se On 15 Jan, 02:59, Alex Skinner wrote: > I'm not sure, maybe its a lucky escape it shows how easy the rug is to > be pulled from underneath you. > > I'll be there see you next month > > A > > On Jan 14, 11:17 am, Jason Blum wrote: > > > > > > > > > Definitely very disappointing. And totally agree GAE would have a lot > > to offer, if they could just fix that bug. > > > The good news is a lot of other folks are stepping in to fill that > > easy one-click cloud deployment space! > > > Join us next month athttp://OpenCFSummit.orgtolearn more! > > > On Jan 13, 5:19 pm, Alex Skinner wrote: > > > > Hi Guys, > > > > At last years OpenCFSummit the Java Google App engine got quite a lot of > > > press, people were assisted in setting it up and deploying their apps and > > > there was a lot of excitement. > > > > The combination of the Open Bluedragon desktop edition and GAE is > > > certainly > > > one of the easiest ways of deploying a ColdFusion or Web application. > > > > Since 1.5 the OpenBluedragon GAE compatibility has been effectively > > > derailed until this bug is > > > fixedhttp://code.google.com/p/googleappengine/issues/detail?id=5898. > > > > It would be nice if the project could announce at the conference that this > > > compatibility has been restored. > > > > Alex -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
