[appengine-java] Re: GAE domains not resolving
Since when did Google App Engine start using Googe Apps to manage domains exclusively? On Aug 31, 3:39 pm, footy anuj.hoo...@gmail.com wrote: Okay, consider what you mentione being the case where I haven't added the subdomain to my app properly. So hence my question is why was it working until 29th August when we have not made any changes to app settings, code or anything else related to the app. Is there anything new that GAE team has done causing this to break? Is there a new requirement or a required setting? Is there something wrong with ghs.google.com? On Aug 31, 1:04 pm, John Patterson jdpatter...@gmail.com wrote: On 31/08/2011 18:36, footy wrote: That is the 404 error page from Google which is what led me to believe that there is a probelm with ghs.google.com and CNAME resolution. The fact that your browser shows this google page indicates that the name resolution is working but that perhaps you have not added the subdomain to your app. -- 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] GAE domains not resolving
We have our domain name http://dev.footygame.com/ with CNAME pointing to ghs.google.com It was working fine until 29th August when the CNAME stopped resolving If you visit that URL now we get 404 What's going on? and how do you resolve it? -- 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: GAE domains not resolving
Oh also, just to mention we are in UK as well. With a proxy like hidemyass.com we still get 404 Also, I noticed something new that appeared in the GAE admin panel under AdministrationApplication Settings you have a few new options; to do with 'Performance'. So could it be that this was a breaking change? On Aug 31, 10:57 am, mscwd01 mscw...@gmail.com wrote: I've noticed the same thing with our domain. However, it seems like a localised issue as I cannot reach my app from home but can at work. Also using a proxy server located in the US loads the site fine (I'm in the UK). Any news on why this may be would be great. On Aug 31, 10:20 am, footy anuj.hoo...@gmail.com wrote: We have our domain namehttp://dev.footygame.com/ with CNAME pointing to ghs.google.com It was working fine until 29th August when the CNAME stopped resolving If you visit that URL now we get 404 What's going on? and how do you resolve it? -- 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: GAE domains not resolving
Another thing that's worth mentioning is that the application works fine with it's Application Default Version URL On Aug 31, 10:57 am, mscwd01 mscw...@gmail.com wrote: I've noticed the same thing with our domain. However, it seems like a localised issue as I cannot reach my app from home but can at work. Also using a proxy server located in the US loads the site fine (I'm in the UK). Any news on why this may be would be great. On Aug 31, 10:20 am, footy anuj.hoo...@gmail.com wrote: We have our domain namehttp://dev.footygame.com/ with CNAME pointing to ghs.google.com It was working fine until 29th August when the CNAME stopped resolving If you visit that URL now we get 404 What's going on? and how do you resolve it? -- 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: GAE domains not resolving
That is the 404 error page from Google which is what led me to believe that there is a probelm with ghs.google.com and CNAME resolution. As mentioned in one of above replies, we did try a proxy in US and we get the same 404 page. and as expected for you in Thailand you get the same. Also, we haven't made any change to our code or application or application setting over the last 2 weeks ( during the application was working fine ) until 29th August. On Aug 31, 12:01 pm, John Patterson jdpatter...@gmail.com wrote: When I try your link from Thailand it resolves to Google but gives this error https://lh3.googleusercontent.com/-sO3H5YHOxdY/Tl4UFX-zLHI/AD... So it looks like your domain issues are local but you have not added the domain to your app correctly. BTW, I also experienced such a local DNS problem that resolved itself within a day. -- 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: GAE domains not resolving
Okay, consider what you mentione being the case where I haven't added the subdomain to my app properly. So hence my question is why was it working until 29th August when we have not made any changes to app settings, code or anything else related to the app. Is there anything new that GAE team has done causing this to break? Is there a new requirement or a required setting? Is there something wrong with ghs.google.com? On Aug 31, 1:04 pm, John Patterson jdpatter...@gmail.com wrote: On 31/08/2011 18:36, footy wrote: That is the 404 error page from Google which is what led me to believe that there is a probelm with ghs.google.com and CNAME resolution. The fact that your browser shows this google page indicates that the name resolution is working but that perhaps you have not added the subdomain to your app. -- 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: java.io.NotSerializableException
I am having similar issue with com.google.appengine.api.datastore.LazyList but it's to do with writing to Memcache. I haven't changed anything in the application either. Got any idea? I have posted here: http://groups.google.com/group/google-appengine-java/browse_thread/thread/ea9b91efb23c46a6 On Mar 27, 12:00 am, Melanie Kirchner kirchner.mela...@googlemail.com wrote: Hi, my app is having some problems lately. I haven't changed anything and since some hours I'm getting the following exception during the login proccess (load data from the DB, store them in the session and redirecht to another page). java.lang.RuntimeException: java.io.NotSerializableException: com.google.appengine.api.datastore.LazyList at com.google.apphosting.runtime.jetty.SessionManager.serialize(SessionManager.java: 393) at com.google.apphosting.runtime.jetty.SessionManager.createEntityForSession(SessionManager.java: 370) at com.google.apphosting.runtime.jetty.SessionManager $AppEngineSession.save(SessionManager.java:164) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java: 41) 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: 238) 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.handleRequest(JavaRuntime.java: 261) at com.google.apphosting.base.RuntimePb$EvaluationRuntime $2.handleRequest(RuntimePb.java:9285) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java: 437) at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java: 573) at com.google.tracing.TraceContext$TraceContextRunnable $1.run(TraceContext.java:448) at com.google.tracing.TraceContext.runInContext(TraceContext.java: 688) at com.google.tracing.TraceContext $AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java: 326) at com.google.tracing.TraceContext $AbstractTraceContextCallback.runInInheritedContext(TraceContext.java: 318) at com.google.tracing.TraceContext $TraceContextRunnable.run(TraceContext.java:446) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: 1110) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.io.NotSerializableException: com.google.appengine.api.datastore.LazyList at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java: 1173) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java: 343) at java.util.HashMap.writeObject(HashMap.java:1018) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 43) at java.lang.reflect.Method.invoke(Method.java:616) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java: 962) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java: 1478) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java: 1409) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java: 1167) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java: 343) at com.google.apphosting.runtime.jetty.SessionManager.serialize(SessionManager.java: 390) ...
[appengine-java] MemcacheServiceImpl
My app is having sudden problem with MemcacheService Has something changed? This is the error I am receving. There has been no code change that I have made and the app has been working fine since quite sometime. Caused by: java.lang.IllegalArgumentException: can't accept class com.google.appengine.api.datastore.LazyList as a memcache entity at com.google.appengine.api.memcache.MemcacheSerialization.serialize(MemcacheSerialization.java: 262) at com.google.appengine.api.memcache.MemcacheServiceImpl.doPut(MemcacheServiceImpl.java: 388) at com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java: 443) -- 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.
