[google-appengine] Re: Twitter issues
We're still seeing issues hitting Twitter. I'm seeing a failure rate of about 1/10: Response: com.google.apphosting.api.ApiProxy$ApplicationException: ApplicationError: 2: Unknown at com.google.apphosting.runtime.ApiProxyImpl $AsyncApiFuture.rpcFinished(ApiProxyImpl.java:322) at com.google.net.rpc.RpcStub$RpcCallbackDispatcher $1.runInContext(RpcStub.java:1025) 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 com.google.net.rpc.RpcStub $RpcCallbackDispatcher.rpcFinished(RpcStub.java:1046) at com.google.net.rpc.RPC.internalFinish(RPC.java:2038) at com.google.net.rpc.impl.RpcNetChannel.finishRpc(RpcNetChannel.java: 2352) at com.google.net.rpc.impl.RpcNetChannel.messageReceived(RpcNetChannel.java: 1279) at com.google.net.rpc.impl.RpcConnection.parseMessages(RpcConnection.java: 319) at com.google.net.rpc.impl.RpcConnection.dataReceived(RpcConnection.java: 290) at com.google.net.async.Connection.handleReadEvent(Connection.java:474) at com.google.net.async.EventDispatcher.processNetworkEvents(EventDispatcher.java: 831) at com.google.net.async.EventDispatcher.internalLoop(EventDispatcher.java: 207) at com.google.net.async.EventDispatcher.loop(EventDispatcher.java: 103) at com.google.net.async.GlobalEventRegistry $2.runLoop(GlobalEventRegistry.java:95) at com.google.net.async.LoopingEventDispatcher $EventDispatcherThread.run(LoopingEventDispatcher.java:384) On Sep 27, 8:32 pm, "Sean Lynch (Google)" wrote: > Things should be working properly now. > > On Sep 28, 12:36 pm, nischalshetty wrote: > > > > > Keeping fingers crossed, hope this gets sorted out soon. > > > -Nischal > > > On Sep 28, 6:46 am, "Ikai Lan (Google)" > > wrote: > > > > Hey everybody, > > > > We're currently being blocked by Twitter. We're reaching out right now to > > > the Twitter team to resolve the issues. > > > > -- > > > Ikai Lan > > > Developer Programs Engineer, Google App Engine > > > Blogger:http://googleappengine.blogspot.com > > > Reddit:http://www.reddit.com/r/appengine > > > Twitter:http://twitter.com/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 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.
[google-appengine] Re: Twitter issues
Yeah, we've escalated to the Twitter folks on our end. It's tough on our end because we don't have a list of IP ranges. I think that the Twitter API folks need to start parsing the app-id portion of User- Agent for their rate-limiting and blacklists for the set of external IPs that GAE users - I'll try to communicate that to the resources we have. We've worked around it ourselves by putting together an external Twitter API proxy based on nginx. If anyone is interested in the Twitter4J patches required to sign OAuth requests for one host, but deliver them to a proxy, let me know. On Sep 28, 8:27 pm, "Ikai Lan (Google)" wrote: > Have you guys raised this with the Twitter API team? We do our best to > resolve issues when App Engine IP addresses become blocked, but it's > important that you voice your concerns with their team as well. As cloud > based solutions become more prominent, IP range based blocking will become > too much of a "nuclear options" for dealing with spam/abuse. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/appengine > Twitter:http://twitter.com/app_engine > > On Mon, Sep 27, 2010 at 8:50 PM, Matt Mastracci wrote: > > > > > We're still seeing issues hitting Twitter. I'm seeing a failure rate > > of about 1/10: > > > Response: com.google.apphosting.api.ApiProxy$ApplicationException: > > ApplicationError: 2: Unknown at > > com.google.apphosting.runtime.ApiProxyImpl > > $AsyncApiFuture.rpcFinished(ApiProxyImpl.java:322) at > > com.google.net.rpc.RpcStub$RpcCallbackDispatcher > > $1.runInContext(RpcStub.java:1025) 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.jav > > a: > > 326) at com.google.tracing.TraceContext > > $AbstractTraceContextCallback.runInInheritedContext(TraceContext.java: > > 318) at com.google.tracing.TraceContext > > $TraceContextRunnable.run(TraceContext.java:446) at > > com.google.net.rpc.RpcStub > > $RpcCallbackDispatcher.rpcFinished(RpcStub.java:1046) at > > com.google.net.rpc.RPC.internalFinish(RPC.java:2038) at > > com.google.net.rpc.impl.RpcNetChannel.finishRpc(RpcNetChannel.java: > > 2352) at > > com.google.net.rpc.impl.RpcNetChannel.messageReceived(RpcNetChannel.java: > > 1279) at > > com.google.net.rpc.impl.RpcConnection.parseMessages(RpcConnection.java: > > 319) at > > com.google.net.rpc.impl.RpcConnection.dataReceived(RpcConnection.java: > > 290) at > > com.google.net.async.Connection.handleReadEvent(Connection.java:474) > > at > > > com.google.net.async.EventDispatcher.processNetworkEvents(EventDispatcher.j > > ava: > > 831) at > > com.google.net.async.EventDispatcher.internalLoop(EventDispatcher.java: > > 207) at com.google.net.async.EventDispatcher.loop(EventDispatcher.java: > > 103) at com.google.net.async.GlobalEventRegistry > > $2.runLoop(GlobalEventRegistry.java:95) at > > com.google.net.async.LoopingEventDispatcher > > $EventDispatcherThread.run(LoopingEventDispatcher.java:384) > > > On Sep 27, 8:32 pm, "Sean Lynch (Google)" wrote: > > > Things should be working properly now. > > > > On Sep 28, 12:36 pm, nischalshetty wrote: > > > > > Keeping fingers crossed, hope this gets sorted out soon. > > > > > -Nischal > > > > > On Sep 28, 6:46 am, "Ikai Lan (Google)" > > > > > > > > > wrote: > > > > > > Hey everybody, > > > > > > We're currently being blocked by Twitter. We're reaching out right > > now to > > > > > the Twitter team to resolve the issues. > > > > > > -- > > > > > Ikai Lan > > > > > Developer Programs Engineer, Google App Engine > > > > > Blogger:http://googleappengine.blogspot.com > > > > > Reddit:http://www.reddit.com/r/appengine > > > > > Twitter:http://twitter.com/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 unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com > e...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- 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 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.
[google-appengine] Re: Twitter issues
e if they've > unblocked all the IPs. I completely agree with you, they should opt > for something else other than IP range blocking for cloud solutions. > > @Matt that seems like a life saver. I have been looking at reverse > proxies the entire day trying to understand what to do. Can you guide > me into this nginx thingy? I too use Twitter4j :) > > One more thing, please voice your concern on this thread -http://is.gd/fyvVp > and star the issue as well. I've been telling them to whitelist based > on user agent but for whatever reason, they do not seem to understand > at all! > > -Nischal > > On Sep 29, 1:52 am, Matt Mastracci wrote: > > > > > Yeah, we've escalated to the Twitter folks on our end. It's tough on > > our end because we don't have a list of IP ranges. I think that the > > Twitter API folks need to start parsing the app-id portion of User- > > Agent for their rate-limiting and blacklists for the set of external > > IPs that GAE users - I'll try to communicate that to the resources we > > have. > > > We've worked around it ourselves by putting together an external > > Twitter API proxy based on nginx. If anyone is interested in the > > Twitter4J patches required to sign OAuth requests for one host, but > > deliver them to a proxy, let me know. > > > On Sep 28, 8:27 pm, "Ikai Lan (Google)" > > wrote: > > > > Have you guys raised this with the Twitter API team? We do our best to > > > resolve issues when App Engine IP addresses become blocked, but it's > > > important that you voice your concerns with their team as well. As cloud > > > based solutions become more prominent, IP range based blocking will become > > > too much of a "nuclear options" for dealing with spam/abuse. > > > > -- > > > Ikai Lan > > > Developer Programs Engineer, Google App Engine > > > Blogger:http://googleappengine.blogspot.com > > > Reddit:http://www.reddit.com/r/appengine > > > Twitter:http://twitter.com/app_engine > > > > On Mon, Sep 27, 2010 at 8:50 PM, Matt Mastracci > > > wrote: > > > > > We're still seeing issues hitting Twitter. I'm seeing a failure rate > > > > of about 1/10: > > > > > Response: com.google.apphosting.api.ApiProxy$ApplicationException: > > > > ApplicationError: 2: Unknown at > > > > com.google.apphosting.runtime.ApiProxyImpl > > > > $AsyncApiFuture.rpcFinished(ApiProxyImpl.java:322) at > > > > com.google.net.rpc.RpcStub$RpcCallbackDispatcher > > > > $1.runInContext(RpcStub.java:1025) 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.jav > > > > a: > > > > 326) at com.google.tracing.TraceContext > > > > $AbstractTraceContextCallback.runInInheritedContext(TraceContext.java: > > > > 318) at com.google.tracing.TraceContext > > > > $TraceContextRunnable.run(TraceContext.java:446) at > > > > com.google.net.rpc.RpcStub > > > > $RpcCallbackDispatcher.rpcFinished(RpcStub.java:1046) at > > > > com.google.net.rpc.RPC.internalFinish(RPC.java:2038) at > > > > com.google.net.rpc.impl.RpcNetChannel.finishRpc(RpcNetChannel.java: > > > > 2352) at > > > > com.google.net.rpc.impl.RpcNetChannel.messageReceived(RpcNetChannel.java: > > > > 1279) at > > > > com.google.net.rpc.impl.RpcConnection.parseMessages(RpcConnection.java: > > > > 319) at > > > > com.google.net.rpc.impl.RpcConnection.dataReceived(RpcConnection.java: > > > > 290) at > > > > com.google.net.async.Connection.handleReadEvent(Connection.java:474) > > > > at > > > > > com.google.net.async.EventDispatcher.processNetworkEvents(EventDispatcher.j > > > > ava: > > > > 831) at > > > > com.google.net.async.EventDispatcher.internalLoop(EventDispatcher.java: > > > > 207) at com.google.net.async.EventDispatcher.loop(EventDispatcher.java: > > > > 103) at com.google.net.async.GlobalEventRegistry > > > > $2.runLoop(GlobalEventRegistry.java:95) at > > > > com.google.net.async.LoopingEventDispatcher > > > > $EventDispatcherThread.run(LoopingEventDispatcher.java:384) > > > > > On Sep 27, 8:32 pm, "Sean Lynch (Google)
[google-appengine] Java Error code 104: A problem was encountered with the process that handled this request, causing it to exit
Hey all, Has anyone been seeing a large number of error code 104s today? We haven't made any significant code changes today, but these started showing up in logs, with no additional information. I've tried upgrading our instance types to F2, just in case we're hitting some sort of memory limit, but it doesn't appear to have helped. I've noticed that there's a Java issue on the status screen: could this be related? Attached is a graph showing the milliseconds/request graph, which seems to correlate with the issue we've been seeing. 1. 1. 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. If you see this message frequently, you may be throwing exceptions during the initialization of your application. (Error code 104) 2. 1. -- 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/-/T12g_EHTjigJ. 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. <>
[google-appengine] AppEngine/Java - production crypto broken?
These just started showing up in our logs - we're getting failures on every request (we use an HMAC to authenticate every request). Anyone else seeing it? java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/intercept/java/security/MessageDigest_ java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/intercept/javax/crypto/Mac_ -- 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/-/hfcMeknRsPYJ. 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.
[google-appengine] Re: AppEngine/Java - production crypto broken?
cheersapp On Tuesday, June 19, 2012 3:22:06 PM UTC-6, Nate White wrote: > > App id, please? > > On Tuesday, June 19, 2012 2:17:58 PM UTC-7, Matt Mastracci wrote: >> >> These just started showing up in our logs - we're getting failures on every >> request (we use an HMAC to authenticate every request). Anyone else seeing >> it? >> >> java.lang.NoClassDefFoundError: >> com/google/apphosting/runtime/security/shared/intercept/java/security/MessageDigest_ >> >> java.lang.NoClassDefFoundError: >> com/google/apphosting/runtime/security/shared/intercept/javax/crypto/Mac_ >> >> >> >> -- 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/-/uyA1-Cbb3asJ. 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.
[google-appengine] Re: Blobstore upload is failing with mysterious "signature verification failed" redirect
That tweet above was mine. We've been seeing this message pop up on and off on http://gri.pe and I've been working on solutions for the last few days. I've seen this redirect happen if your uploader modifies the URL at all. This includes appending anything to the path or adding a query string. We've also been seeing otherwise valid blobstore upload URLs get invalidated on occasion on http://gri.pe, but I haven't done enough testing to rule out some sort of expiry/timeout. The plupload library works great for uploading to the blobstore, but by default it adds ?name= to the upload URL, breaking the blobstore URL signature and causing that error. I've got a patched version up on our site that only supports the html4 and html5 upload methods, but is verified tested across all browsers against the blobstore upload URLs in prod and dev. If you want, I can dig out the unminified source too: http://www.gri.pe/static/plupload/plupload.full.min.js On Nov 15, 9:26 am, "Gijs (Cloudwise)" wrote: > I got the same problems using the blobstore. All I want is uploading > files to the blobstore using AJAX(-like) functionallity. I > triedhttp://valums.com/ajax-upload/andhttp://jquery.malsup.com/form/#file-upload > both javascript plugings for jQuery. All works fine in the dev > environment, but in production it simply doesn't work. While digging > in the response I found this "signature verification failed" message. > Anyone any idea? > > On 13 nov, 22:29, Michael Bayne wrote: > > > > > > > > > I just added upload support to my app using the BlobStore. Everything > > works peachily in the dev environment, but now that I'm trying to use > > the functionality in production, uploads are resulting in a redirect > > to "http://www.google.com/search?q=signature+verification+failed"; which > > is rather mysterious to say the least. > > > Not that those results are visible in my app, since I am doing the > > uploading via GWT, but when I look at the results manually, they don't > > yield anything particularly informative. > > > The only thing I've been able to find on the Interwebs about this at > > all is one guy's tweet saying: > > > If you find your AppEngine app on upload randomly redirecting people to > > a search for "signature verification failed", that's a blobstore bug > > > This was from a few days ago. No indication of any workarounds, or if > > perhaps this might get fixed. Is the blobstore just broken right now? -- 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 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.
