Re: [google-appengine] Avanced sort expressions in Search feature (Java)
hi, How about adding a query filter on that field? E.g., say this numeric field is called 'ranking'. Your query could include: ranking 0 along with any other search terms. E.g. if you also want to look for the word 'books', your query would look like: books ranking 0 Then, define the sort expression to order on that field in ascending order. On 12 September 2012 02:54, Jordi P.S. planad...@gmail.com wrote: Hello, I have a question concerning the SortExpression: I'd like to sort a list of documents in Ascending order. I'd like to avoid the 0 or negative values, which I'd put them at the end of the list. Is there a way to do it with a sort expression? Example list: 1 0 4 5 2 Sorted list: 1 2 4 5 0 Any idea? I'm thinking in something like: sortexpression=MAX_DOUBLE+field_name Jordi. -- 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/-/AlCFVki-VKsJ. 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. -- 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-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.
Re: [google-appengine] openid4java suddenly stopped working
Hi Alexander, It should be OK now. Let me know if you still have the problem. -- Takashi On Tue, Sep 11, 2012 at 8:04 PM, Alexander Botov alexbo...@absolutns.comwrote: Greetings, Today we found out that our Google Apps Open ID related code suddenly stopped working resulting in blocking of all Open ID sign-ins. We use openid4java, the very bottom of the stack trace it shows the real cause: *Caused by: java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/stub/javax/net/ssl/SSLContext * * at java.lang.Class.getDeclaredConstructors0(Native Method)* * at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)* * ... 126 more* *Caused by: java.lang.ClassNotFoundException: com.google.apphosting.runtime.security.shared.stub.javax.net.ssl.SSLContext * * at com.google.appengine.runtime.Request.process-ef6eb452cfea3de1(Request.java) * * ... 126 more* This is initiated from guice and openid4java, the root exception is: *Caused by: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: Unable to get members for class org.openid4java.util.HttpFetcherFactory* HttpFetcherFactory can be constructed with SSLContext as parameter, I guess something changed in the hosting environment that causes this code to be no longer working. Locally everything works just fine. Any help? This is urgent request, the problem happens on production server currently. Best Regards, --alex -- 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/-/5-gu-UElC_cJ. 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. -- Takashi Matsuo | Developers Advocate | tmat...@google.com -- 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-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.
Re: [google-appengine] Avanced sort expressions in Search feature (Java)
I need all the elements: the ones that ranking 0 and the ones that ranking = 0. As you say I could do 2 searchs the first with a query filter 0 and the other with the query filter = 0 and unify them in the application logic. This would be a solution but, do you think there is a solution with only 1 search ? On Wed, Sep 12, 2012 at 9:47 AM, Amy Unruh amyu+gro...@google.com wrote: hi, How about adding a query filter on that field? E.g., say this numeric field is called 'ranking'. Your query could include: ranking 0 along with any other search terms. E.g. if you also want to look for the word 'books', your query would look like: books ranking 0 Then, define the sort expression to order on that field in ascending order. On 12 September 2012 02:54, Jordi P.S. planad...@gmail.com wrote: Hello, I have a question concerning the SortExpression: I'd like to sort a list of documents in Ascending order. I'd like to avoid the 0 or negative values, which I'd put them at the end of the list. Is there a way to do it with a sort expression? Example list: 1 0 4 5 2 Sorted list: 1 2 4 5 0 Any idea? I'm thinking in something like: sortexpression=MAX_DOUBLE+field_name Jordi. -- 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/-/AlCFVki-VKsJ. 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. -- 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-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. -- 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-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] orphaned gae application
I have a gae application without administrator. It's because we delete de administrator account from the google apps control panel, so i need to add a new one administrator. I was searching for this during days without success. Any help?! Thanks in advance. =) -- 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/-/zI58Soun7RgJ. 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.
Re: [google-appengine] Re: Oops! We couldn't retrieve your list of Kinds. Datastore API, Datastore Viewer and Datastore Admin problems
Guys, If you dont see the NameSpace dropdown you can still see the data using following type of query. SELECT * FROM NameSpaceEntity E.g. SELECT * FROM TEST_NSCompany Hope this helps. Regards, Vinay On Monday, May 9, 2011 9:12:56 AM UTC+5:30, Robert Kluin wrote: Hey Roberto, You have stored data, right? A kind will not list in the datastore viewer / admin unless data is already in the datastore. Out of curiosity, why are you unable to write a script to clear out your data? If you have data stored and nothing is listing, you might try submitting a production issue: http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue Robert On Sun, May 8, 2011 at 16:33, roberto.cr rober...@gmail.com javascript: wrote: Has no one faced this problem and solved it? Should I directly contact the appengine team about this? What's the best way for me to do so? On May 7, 5:20 am, roberto.cr roberto...@gmail.com wrote: Hey Robert, thanks for your reply!! :) I'm not using any namespaces. Options 1 and 2 doesn't work, as described. Option 3 doesn't work either (*) Which makes me think Option 4 won't either I've tried searching on this group for other problems like this, but with no solution. This feels beyond my reach. Does anyone know the real cause of this problem? (*) is there a nicer admin tool for the datastore? like the ones mysql has? I miss a lot of things... On May 7, 1:01 am, Robert Kluin robert.kl...@gmail.com wrote: Hey Roberto, Are you using namespaces? You have to delete all of the entities. Some ways you could do this 1) using the datastore admin, 2) using the datastore viewer (if there is little data), 3) by writing a script to do it, 4) using the remote api. It sounds like options 1 and 2 won't work for you, since you can't seem to get kind lists. Robert On Fri, May 6, 2011 at 14:06, roberto.cr roberto...@gmail.com wrote: yes, it's been days actually is there a way to completely flush the datastore? I'm pretty sure my code is correct, this really seems beyond my reach... On May 6, 12:12 pm, Robert Kluin robert.kl...@gmail.com wrote: Hey Roberto, Have you wrote any data to the datastore? Also, sometimes there is a little delay before changes are reflected in the kinds lists. Robert On Fri, May 6, 2011 at 01:40, roberto.cr roberto...@gmail.com wrote: I've deployed the last version of my app (only small changes in datastore models), which is perfect locally, but has caused weird problems (both on the dashboard and the app itself): App problem: it cannot read/write using the datastore api (I'm using python, but it doesn't matter here I guess) Datastore Viewer problem: Oops! We couldn't retrieve your list of Kinds. Please try again later. Datastore Admin problem: displays a blank page on the right (only the regular menu on the left and top) I really believe something beyond my reach has happened, that's why I'm asking here the app id is qperto Thanks! -- 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-a...@googlegroups.com javascript:. To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group athttp:// 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-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group athttp:// 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-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/-DsmB-gUGJ4J. 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.
Re: [google-appengine] Avanced sort expressions in Search feature (Java)
In order to do it in one query, you could add a field that is used specifically for sorting. If the value of the normal field is positive, the sort field would be the same as the normal field. If the value of the normal field is negative or zero, the sort field could be something like: - normal field. This would work as long as there's a known upper limit of the value of the normal positive field. On Wednesday, September 12, 2012 3:05:35 AM UTC-5, Jordi P.S. wrote: I need all the elements: the ones that ranking 0 and the ones that ranking = 0. As you say I could do 2 searchs the first with a query filter 0 and the other with the query filter = 0 and unify them in the application logic. This would be a solution but, do you think there is a solution with only 1 search ? On Wed, Sep 12, 2012 at 9:47 AM, Amy Unruh amyu+...@google.comjavascript: wrote: hi, How about adding a query filter on that field? E.g., say this numeric field is called 'ranking'. Your query could include: ranking 0 along with any other search terms. E.g. if you also want to look for the word 'books', your query would look like: books ranking 0 Then, define the sort expression to order on that field in ascending order. On 12 September 2012 02:54, Jordi P.S. plan...@gmail.com javascript:wrote: Hello, I have a question concerning the SortExpression: I'd like to sort a list of documents in Ascending order. I'd like to avoid the 0 or negative values, which I'd put them at the end of the list. Is there a way to do it with a sort expression? Example list: 1 0 4 5 2 Sorted list: 1 2 4 5 0 Any idea? I'm thinking in something like: sortexpression=MAX_DOUBLE+field_name Jordi. -- 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/-/AlCFVki-VKsJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. 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-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/_ZMYPzrhEvAJ. 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.
Re: [google-appengine] openid4java suddenly stopped working
Hi Takashi, All seems to be working right now. Thanks for the fast resolution! On Wednesday, September 12, 2012 10:54:08 AM UTC+3, Takashi Matsuo (Google) wrote: Hi Alexander, It should be OK now. Let me know if you still have the problem. -- Takashi On Tue, Sep 11, 2012 at 8:04 PM, Alexander Botov alex...@absolutns.comjavascript: wrote: Greetings, Today we found out that our Google Apps Open ID related code suddenly stopped working resulting in blocking of all Open ID sign-ins. We use openid4java, the very bottom of the stack trace it shows the real cause: *Caused by: java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/stub/javax/net/ssl/SSLContext * * at java.lang.Class.getDeclaredConstructors0(Native Method)* * at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)* * ... 126 more* *Caused by: java.lang.ClassNotFoundException: com.google.apphosting.runtime.security.shared.stub.javax.net.ssl.SSLContext * * at com.google.appengine.runtime.Request.process-ef6eb452cfea3de1(Request.java) * * ... 126 more* This is initiated from guice and openid4java, the root exception is: *Caused by: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: Unable to get members for class org.openid4java.util.HttpFetcherFactory* HttpFetcherFactory can be constructed with SSLContext as parameter, I guess something changed in the hosting environment that causes this code to be no longer working. Locally everything works just fine. Any help? This is urgent request, the problem happens on production server currently. Best Regards, --alex -- 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/-/5-gu-UElC_cJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Takashi Matsuo | Developers Advocate | tma...@google.com javascript: -- 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/-/cA-MPXC2kaYJ. 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: 1.7.1 Pre-release SDKs Available
As mentioned in the release notes - The Mail API now supports the following headers for outgoing mail: List-Id, List-Unsubscribe, On-Behalf-Of, Resent-Date, Resent-From, Resent-To I tried to to add two headers for test run, here are the populated headers in the log. List-Id: mylistid677 List-Unsubscribe: unsubfroml...@mydomain.com However when I checked email source there were no such headers populated. I am using JAVA SDK 1.7.1 Please find the code for same. msg.setHeader(List-Id, mylistid677); msg.setHeader(List-Unsubscribe, unsubfroml...@mydomain.com); What am I missing in code or application setting ? Or these headers are still not supported ? On Wednesday, August 8, 2012 11:27:54 PM UTC+5:30, Marce (Google) wrote: Hi, We've just posted the pre-release SDKs for Python and Java here: http://code.google.com/p/googleappengine/downloads/list Release notes below. Cheers, Marzia App Engine Java SDK - Release NotesVersion 1.7.1=- The URLFetch API now supports multiple cookie headers. http://code.google.com/p/googleappengine/issues/detail?id=3379 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D3379usg=AFQjCNGmMC_rdHesW_2aGQpFJYrpuhU6WA- You can download 90 days worth of Usage Reports for your application from the Billing History page of the Admin Console.- Task Queue requests now include an X-AppEngine-TaskExecutionCount that counts the number of times a task was run by an instance.- Added support for delete() to the Files API.- Added support for multiple files to be deleted using the Files API.- Added support to delete files from Google Cloud Storage using the Files API.- Added a REQUEST_LOG_ID to be written in the logs and as an ApiProxy.Environment attribute. This can be used to later identifying that request in the application logs.- The Memcache Viewer now supports namespaces. http://code.google.com/p/googleappengine/issues/detail?id=7245 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7245usg=AFQjCNHLF4TbAjowkpD30Vv1WeedSF8fNQ- The Mail API now supports the following headers for outgoing mail: List-Id, List-Unsubscribe, On-Behalf-Of, Resent-Date, Resent-From, Resent-To. http://code.google.com/p/googleappengine/issues/detail?id=2559 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D2559usg=AFQjCNGkfYOxsryN2URgym-bM95SzSzY5A http://code.google.com/p/googleappengine/issues/detail?id=7672 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7672usg=AFQjCNEiNLuhDHmbptGbtNNqGuHLXAfCVg- Version 2 of the DataNucleus plugin has been upgraded and is now fully supported. For a full list of improvements please see http://code.google.com/p/datanucleus-appengine/source/browse/branches/2_1_0/dist/RELEASE_NOTES.ORM http://www.google.com/url?q=http://code.google.com/p/datanucleus-appengine/source/browse/branches/2_1_0/dist/RELEASE_NOTES.ORMusg=AFQjCNGuSieUqsa1x4Oo_E41WONDPE6-sw- The Search API now supports default values for dates in SortExpressions.- The .project and .classpath files are now included in the App Engine demos so that they may be imported by Eclipse.- Fixed an issue with the App Engine satisfaction survey in the Admin Console which was released in 1.6.6, which will be re-enabled in this release.- Fixed an issue where ListIndexes failed when trying to return a schema that contained Geo fields.- Fixed an issue with Search API websafe cursors not being returned as a websafe value.- Fixed an issue where Java's AsyncMemcacheServiceImpl was incorrectly throwing MemcacheServiceException. http://code.google.com/p/googleappengine/issues/detail?id=6236 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D6236usg=AFQjCNF2MoPaIbrPA4v3jw_1RDWnmIHBCQ- Fixed a Memcache error when getting HttpSession. http://code.google.com/p/googleappengine/issues/detail?id=6463 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D6463usg=AFQjCNHHXE0yoIvT2Ebankiah6JFFfWkYg- Fixed a search issue where snippets failed to highlight when a capital letter is used in a search term. http://code.google.com/p/googleappengine/issues/detail?id=7665 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7665usg=AFQjCNG1w2dqWb4m7lCZfm673pDXWUW22w- Fixed an issue where JDO and JPA keys-only queries were being executed as full entity queries in the datastore. http://code.google.com/p/googleappengine/issues/detail?id=7712 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7712usg=AFQjCNGNYu2C5bs8LrrdNZVdk9d6ezl91Q- Fixed an issue where traffic splitting by cookie was not working. http://code.google.com/p/googleappengine/issues/detail?id=7813
Re: [google-appengine] openid4java suddenly stopped working
we have the same problem : javax.servlet.ServletContext log: unavailable com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: * Unable to get members for class org.openid4java.util.HttpFetcherFactory* at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:553) at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:419) at com.google.inject.internal.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2041) at com.google.inject.internal.FailableCache.get(FailableCache.java:46) at com.google.inject.MembersInjectorStore.get(MembersInjectorStore.java:66) On Wednesday, 12 September 2012 10:54:08 UTC+3, Takashi Matsuo (Google) wrote: Hi Alexander, It should be OK now. Let me know if you still have the problem. -- Takashi On Tue, Sep 11, 2012 at 8:04 PM, Alexander Botov alex...@absolutns.comjavascript: wrote: Greetings, Today we found out that our Google Apps Open ID related code suddenly stopped working resulting in blocking of all Open ID sign-ins. We use openid4java, the very bottom of the stack trace it shows the real cause: *Caused by: java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/stub/javax/net/ssl/SSLContext * * at java.lang.Class.getDeclaredConstructors0(Native Method)* * at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)* * ... 126 more* *Caused by: java.lang.ClassNotFoundException: com.google.apphosting.runtime.security.shared.stub.javax.net.ssl.SSLContext * * at com.google.appengine.runtime.Request.process-ef6eb452cfea3de1(Request.java) * * ... 126 more* This is initiated from guice and openid4java, the root exception is: *Caused by: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: Unable to get members for class org.openid4java.util.HttpFetcherFactory* HttpFetcherFactory can be constructed with SSLContext as parameter, I guess something changed in the hosting environment that causes this code to be no longer working. Locally everything works just fine. Any help? This is urgent request, the problem happens on production server currently. Best Regards, --alex -- 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/-/5-gu-UElC_cJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Takashi Matsuo | Developers Advocate | tma...@google.com javascript: -- 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/-/vY9ZJFziZlwJ. 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] SDK 1.7.1 Mail Headers
As per SDK 1.7.1 Release notes - The Mail API now supports the following headers for outgoing mail: List-Id, List-Unsubscribe, On-Behalf-Of, Resent-Date, Resent-From, Resent-To. But these headers are still not getting populated. Any one got success in populating *List-Id* or *List-Unsubscribe* headers using Java SDK 1.7.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/-/rBCzTdUIpAsJ. 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.
Re: [google-appengine] openid4java suddenly stopped working
Hi Mihai, What is your app-id? On Wed, Sep 12, 2012 at 11:40 PM, Mihai mi...@epek.com wrote: we have the same problem : javax.servlet.ServletContext log: unavailable com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: * Unable to get members for class org.openid4java.util.HttpFetcherFactory* at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:553) at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:419) at com.google.inject.internal.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2041) at com.google.inject.internal.FailableCache.get(FailableCache.java:46) at com.google.inject.MembersInjectorStore.get(MembersInjectorStore.java:66) On Wednesday, 12 September 2012 10:54:08 UTC+3, Takashi Matsuo (Google) wrote: Hi Alexander, It should be OK now. Let me know if you still have the problem. -- Takashi On Tue, Sep 11, 2012 at 8:04 PM, Alexander Botov alex...@absolutns.comwrote: Greetings, Today we found out that our Google Apps Open ID related code suddenly stopped working resulting in blocking of all Open ID sign-ins. We use openid4java, the very bottom of the stack trace it shows the real cause: *Caused by: java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/stub/javax/ net/ssl/SSLContext* * at java.lang.Class.getDeclaredConstructors0(Native Method)* * at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)* * ... 126 more* *Caused by: java.lang.ClassNotFoundException: com.google.apphosting.runtime.security.shared.stub.javax. net.ssl.SSLContext* * at com.google.appengine.runtime.Request.process- ef6eb452cfea3de1(Request.java)* * ... 126 more* This is initiated from guice and openid4java, the root exception is: *Caused by: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: Unable to get members for class org.openid4java.util.HttpFetcherFactory* HttpFetcherFactory can be constructed with SSLContext as parameter, I guess something changed in the hosting environment that causes this code to be no longer working. Locally everything works just fine. Any help? This is urgent request, the problem happens on production server currently. Best Regards, --alex -- 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/-/5-gu-**UElC_cJhttps://groups.google.com/d/msg/google-appengine/-/5-gu-UElC_cJ . To post to this group, send email to google-a...@googlegroups.**com. To unsubscribe from this group, send email to google-appengi...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/google-appengine?hl=enhttp://groups.google.com/group/google-appengine?hl=en . -- Takashi Matsuo | Developers Advocate | tma...@google.com -- 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/-/vY9ZJFziZlwJ. 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. -- Takashi Matsuo | Developers Advocate | tmat...@google.com -- 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-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.
Re: [google-appengine] Speeding up memcache by 3x for datastore entities
JSON will not beat python's marshal. It wont even come close. See my other blogpost: http://devblog.miumeet.com/2012/06/storing-json-efficiently-in-python-on.html It also discusses zip options on marshalled data. Cheers, -Andrin On Wed, Sep 5, 2012 at 7:53 PM, Drake drak...@digerat.com wrote: Proto-buffers are mostly fast, but not always. And they are typically larger, I think more info about the objects are stored. -Original Message- From: google-appengine@googlegroups.com [mailto:google- appeng...@googlegroups.com] On Behalf Of Jeff Schnitzer Sent: Wednesday, September 05, 2012 10:27 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Speeding up memcache by 3x for datastore entities Have you compared this against the performance of ndb's integrated caching? I believe it uses protocol buffers. Also, getting entity cache behavior right - so that contention doesn't throw the cache out of sync - is very hard. Jeff On Wed, Sep 5, 2012 at 9:32 AM, Drake drak...@digerat.com wrote: Yes, this has been discussed before. We use marshal for a lot of our stuff, but it isn't always faster. It depends on how large the objects are and the types. The size difference is interesting, as we rarely see that. You should also benchmark against JSON which is often faster than Marshall, and often smaller. Lastly you should bench each with Zip compression. The size of the object does matter, and at different compression levels you get different performance curves. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Andrin von Rechenberg Sent: Wednesday, September 05, 2012 2:15 AM To: google-appengine@googlegroups.com Subject: [google-appengine] Speeding up memcache by 3x for datastore entities There is an amazingly simple trick how to speed up memcache by 3x for datastore models and entities use only half the size in memcache, see my blogpost: http://devblog.miumeet.com/2012/09/speeding-up-memcache-by-3x- for.html Cheers, -Andrin -- 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-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. -- 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-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. -- 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-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. -- 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-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. -- 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-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: com.google.gwt.user.client.rpc.SerializationException
Hi.
This is not a datastore problem at all, it is a GWT issue.
GWT does not compile all classes to JS, only the ones willing to be used in
the UI. Those are listed in a serialization whitelist. Your class is just
not in the list.
Normally this is done automatically by scanning the RPC. Sometimes is not
done if you use this class for example as a generic. You can force the
whitelisting by implementing the IsSerializable interface. If this still
not work, it might be the case, you have to create dummy methods in your
RPC.
*public void dummy(PackageEnquiryEntity entity); *
This way the autoscan of the RPC is going to add this class to the white
list. There isn't any other way to do so.
BTW, using persistent beans for your presentation layer is usally not a
good practice.
Hope it helps,
Jordi.
On Monday, September 10, 2012 6:47:57 PM UTC+2, Deepak Singh wrote:
Hi All,
I have a deployed running application in following environment GWT 2.5RC1,
GAE 1.7.0, Objectify 3.x
I deleted all previous data from DB. Now for some reason, i changed the
class names of my entities.
All code remains same.
Here i have a entity with new name as follows
@Unindexed
public class PackageEnquiryEntity implements Serializable {
/**
*
*/
private static final long serialVersionUID = -8667552679106180269L;
public PackageEnquiryEntity() {
}
@Id Long id;
@Indexed private String userIdAsEmail;
@Indexed private Date enquiryDate;
I am returning ListPackageEnquiryEntity through many RPC calls.
Everything works fine in development mode. No issue.
But in production mode on GAE, i am getting SerializationException through
some of RPC calls while some RPC calls works fine with the same entity.
I am confused why it fails in production. Everything was working fine in
production also before changing the class names of entity.
Here are the exception details
javax.servlet.ServletContext log: Exception while dispatching incoming RPC
call
com.google.gwt.user.client.rpc.SerializationException: Type
'com.pdstechi.commonmodule.shared.holiday.PackageEnquiryEntity' was not
included in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For security
purposes, this type will not be serialized.: instance =
com.pdstechi.commonmodule.shared.holiday.PackageEnquiryEntity@d8a125
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:665)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:126)
at
com.google.gwt.user.client.rpc.core.java.util.Collection_CustomFieldSerializerBase.serialize(Collection_CustomFieldSerializerBase.java:44)
at
com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializer.serialize(ArrayList_CustomFieldSerializer.java:39)
at
com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializer.serializeInstance(ArrayList_CustomFieldSerializer.java:51)
at
com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializer.serializeInstance(ArrayList_CustomFieldSerializer.java:28)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:786)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:667)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:126)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:153)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:585)
at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:605)
at
com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess(RPC.java:471)
at
com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:563)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at
com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
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.appengine.tools.appstats.AppstatsFilter.doFilter(AppstatsFilter.java:141)
at
[google-appengine] Re: 1.7.1 Pre-release SDKs Available
Not entirely sure if this will fix it, but List-Unsubscribe should be a URL format: *mailto:unsubf...@mydomain.com* not just unsubf...@mydomain.com You can include multiple ways to unsubscribe to (mailto: as well as http://) List-Unsubscribe: mailto:identifying_key@app_id.appspotmail.com,http://[url_to_unsubscribe_to] Hope this helps! -Prateek On Wednesday, September 12, 2012 10:32:04 AM UTC-4, AmitAlone wrote: As mentioned in the release notes - The Mail API now supports the following headers for outgoing mail: List-Id, List-Unsubscribe, On-Behalf-Of, Resent-Date, Resent-From, Resent-To I tried to to add two headers for test run, here are the populated headers in the log. List-Id: mylistid677 List-Unsubscribe: unsubf...@mydomain.com javascript: However when I checked email source there were no such headers populated. I am using JAVA SDK 1.7.1 Please find the code for same. msg.setHeader(List-Id, mylistid677); msg.setHeader(List-Unsubscribe, unsubf...@mydomain.com javascript:); What am I missing in code or application setting ? Or these headers are still not supported ? On Wednesday, August 8, 2012 11:27:54 PM UTC+5:30, Marce (Google) wrote: Hi, We've just posted the pre-release SDKs for Python and Java here: http://code.google.com/p/googleappengine/downloads/list Release notes below. Cheers, Marzia App Engine Java SDK - Release NotesVersion 1.7.1=- The URLFetch API now supports multiple cookie headers. http://code.google.com/p/googleappengine/issues/detail?id=3379 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D3379usg=AFQjCNGmMC_rdHesW_2aGQpFJYrpuhU6WA- You can download 90 days worth of Usage Reports for your application from the Billing History page of the Admin Console.- Task Queue requests now include an X-AppEngine-TaskExecutionCount that counts the number of times a task was run by an instance.- Added support for delete() to the Files API.- Added support for multiple files to be deleted using the Files API.- Added support to delete files from Google Cloud Storage using the Files API.- Added a REQUEST_LOG_ID to be written in the logs and as an ApiProxy.Environment attribute. This can be used to later identifying that request in the application logs.- The Memcache Viewer now supports namespaces. http://code.google.com/p/googleappengine/issues/detail?id=7245 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7245usg=AFQjCNHLF4TbAjowkpD30Vv1WeedSF8fNQ- The Mail API now supports the following headers for outgoing mail: List-Id, List-Unsubscribe, On-Behalf-Of, Resent-Date, Resent-From, Resent-To. http://code.google.com/p/googleappengine/issues/detail?id=2559 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D2559usg=AFQjCNGkfYOxsryN2URgym-bM95SzSzY5A http://code.google.com/p/googleappengine/issues/detail?id=7672 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7672usg=AFQjCNEiNLuhDHmbptGbtNNqGuHLXAfCVg- Version 2 of the DataNucleus plugin has been upgraded and is now fully supported. For a full list of improvements please see http://code.google.com/p/datanucleus-appengine/source/browse/branches/2_1_0/dist/RELEASE_NOTES.ORM http://www.google.com/url?q=http://code.google.com/p/datanucleus-appengine/source/browse/branches/2_1_0/dist/RELEASE_NOTES.ORMusg=AFQjCNGuSieUqsa1x4Oo_E41WONDPE6-sw- The Search API now supports default values for dates in SortExpressions.- The .project and .classpath files are now included in the App Engine demos so that they may be imported by Eclipse.- Fixed an issue with the App Engine satisfaction survey in the Admin Console which was released in 1.6.6, which will be re-enabled in this release.- Fixed an issue where ListIndexes failed when trying to return a schema that contained Geo fields.- Fixed an issue with Search API websafe cursors not being returned as a websafe value.- Fixed an issue where Java's AsyncMemcacheServiceImpl was incorrectly throwing MemcacheServiceException. http://code.google.com/p/googleappengine/issues/detail?id=6236 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D6236usg=AFQjCNF2MoPaIbrPA4v3jw_1RDWnmIHBCQ- Fixed a Memcache error when getting HttpSession. http://code.google.com/p/googleappengine/issues/detail?id=6463 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D6463usg=AFQjCNHHXE0yoIvT2Ebankiah6JFFfWkYg- Fixed a search issue where snippets failed to highlight when a capital letter is used in a search term. http://code.google.com/p/googleappengine/issues/detail?id=7665 http://www.google.com/url?q=http://code.google.com/p/googleappengine/issues/detail%3Fid%3D7665usg=AFQjCNG1w2dqWb4m7lCZfm673pDXWUW22w- Fixed an issue where JDO
[google-appengine] APP DOWN: App suddenly no longer starts, no code changes
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.GuiceFilter setPipeline: Multiple Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took 514 millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1479784{/,/base/data/home/apps/s~voost0/2012-09-10-1715.361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:35)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:211)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
at
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39)
at
st.voo.tick.util.GuiceResteasyFilterDispatcher.init(GuiceResteasyFilterDispatcher.java:48)
at
com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:219)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:194)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:134)
at
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:452)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:459)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:701)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:336)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:328)
at
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:456)
at
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.RuntimeException: Unable to instantiate MessageBodyReader
at
org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:761)
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:70)
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:31)
... 27 more
Caused by: java.lang.SecurityException: Unable to get members for
class org.jboss.resteasy.plugins.providers.DataSourceProvider
at
com.google.appengine.runtime.Request.process-b6ca2b194d66ed23(Request.java)
at java.lang.Class.getConstructors(Class.java:291)
at
org.jboss.resteasy.util.PickConstructor.pickSingletonConstructor(PickConstructor.java:27)
at
org.jboss.resteasy.spi.ResteasyProviderFactory.getProviderInstance(ResteasyProviderFactory.java:1032)
at
org.jboss.resteasy.spi.ResteasyProviderFactory.addMessageBodyReader(ResteasyProviderFactory.java:478)
at
org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:757)
at
[google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
HELP!
We have tried everything at this point. Shut down instances, tried to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice error
must be a symptom; the smoking gun seems to be:
java.lang.ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer j...@infohazard.org wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.GuiceFilter setPipeline: Multiple Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took 514
millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1479784{/,/base/data/home/apps/s~voost0/2012-09-10-1715.361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:35)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:211)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
at
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39)
at
st.voo.tick.util.GuiceResteasyFilterDispatcher.init(GuiceResteasyFilterDispatcher.java:48)
at
com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:219)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:194)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:134)
at
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:452)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:459)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:701)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:336)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:328)
at
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:456)
at
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.RuntimeException: Unable to instantiate MessageBodyReader
at
org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:761)
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:70)
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:31)
[google-appengine] Lunch Just Off The Google Campus Today at 1?
If anyone is interested I'm going to grab lunch at the Schwerma Place on Shoreline just off the Google Campus. Feel Free to join me and the couple of people from Stremor.com that are traveling with me. 650-281-1467 -Brandon -- 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/-/b7IEzoncF4QJ. 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: APP DOWN: App suddenly no longer starts, no code changes
More information:
* The failure began at 10:54am (pacific).
* Same app on different appid has the same problem.
(as listed in the stacktraces, the appid is voost0)
Jeff
On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer j...@infohazard.org wrote:
HELP!
We have tried everything at this point. Shut down instances, tried to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice error
must be a symptom; the smoking gun seems to be:
java.lang.ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer j...@infohazard.org wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.GuiceFilter setPipeline: Multiple Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took 514
millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1479784{/,/base/data/home/apps/s~voost0/2012-09-10-1715.361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:35)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:211)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
at
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39)
at
st.voo.tick.util.GuiceResteasyFilterDispatcher.init(GuiceResteasyFilterDispatcher.java:48)
at
com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:219)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:194)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:134)
at
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:452)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:459)
at
com.google.tracing.TraceContext.runInContext(TraceContext.java:701)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:336)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:328)
at
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:456)
at
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.RuntimeException: Unable to instantiate
MessageBodyReader
at
[google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
We are back up and running now after 2 hrs of downtime.
To whoever fixed it: THANK YOU!!!
To whoever broke it in the first place: SPANKINGS!!!
Jeff
On Wed, Sep 12, 2012 at 12:11 PM, Jeff Schnitzer j...@infohazard.org wrote:
More information:
* The failure began at 10:54am (pacific).
* Same app on different appid has the same problem.
(as listed in the stacktraces, the appid is voost0)
Jeff
On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer j...@infohazard.org wrote:
HELP!
We have tried everything at this point. Shut down instances, tried to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice error
must be a symptom; the smoking gun seems to be:
java.lang.ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer j...@infohazard.org wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.GuiceFilter setPipeline: Multiple Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took 514
millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1479784{/,/base/data/home/apps/s~voost0/2012-09-10-1715.361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:35)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:211)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
at
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39)
at
st.voo.tick.util.GuiceResteasyFilterDispatcher.init(GuiceResteasyFilterDispatcher.java:48)
at
com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:219)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:194)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:134)
at
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:452)
at
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:459)
at
com.google.tracing.TraceContext.runInContext(TraceContext.java:701)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:336)
at
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:328)
at
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:456)
at
[google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
I wonder what happened, subscribed to this topic to be updated, hope
someone explains what happened and additionally hope this never happens to
me (python) :)
On Wednesday, September 12, 2012 11:00:49 PM UTC+3, Jeff Schnitzer wrote:
We are back up and running now after 2 hrs of downtime.
To whoever fixed it: THANK YOU!!!
To whoever broke it in the first place: SPANKINGS!!!
Jeff
On Wed, Sep 12, 2012 at 12:11 PM, Jeff Schnitzer
je...@infohazard.orgjavascript:
wrote:
More information:
* The failure began at 10:54am (pacific).
* Same app on different appid has the same problem.
(as listed in the stacktraces, the appid is voost0)
Jeff
On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer
je...@infohazard.orgjavascript:
wrote:
HELP!
We have tried everything at this point. Shut down instances, tried to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice error
must be a symptom; the smoking gun seems to be:
java.lang.ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer
je...@infohazard.orgjavascript:
wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.GuiceFilter setPipeline: Multiple Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took
514 millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1479784{/,/base/data/home/apps/s~voost0/2012-09-10-1715.361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:35)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:211)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
at
org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39)
at
st.voo.tick.util.GuiceResteasyFilterDispatcher.init(GuiceResteasyFilterDispatcher.java:48)
at
com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
at
com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
at
com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at
org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:219)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:194)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:134)
at
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:447)
at
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:452)
at
Re: [google-appengine] openid4java suddenly stopped working
never mind, now it seems to work again . On Wednesday, 12 September 2012 18:04:10 UTC+3, Takashi Matsuo (Google) wrote: Hi Mihai, What is your app-id? On Wed, Sep 12, 2012 at 11:40 PM, Mihai mi...@epek.com javascript:wrote: we have the same problem : javax.servlet.ServletContext log: unavailable com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: * Unable to get members for class org.openid4java.util.HttpFetcherFactory* at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:553) at com.google.inject.internal.MapMaker$StrategyImpl.compute(MapMaker.java:419) at com.google.inject.internal.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2041) at com.google.inject.internal.FailableCache.get(FailableCache.java:46) at com.google.inject.MembersInjectorStore.get(MembersInjectorStore.java:66) On Wednesday, 12 September 2012 10:54:08 UTC+3, Takashi Matsuo (Google) wrote: Hi Alexander, It should be OK now. Let me know if you still have the problem. -- Takashi On Tue, Sep 11, 2012 at 8:04 PM, Alexander Botov alex...@absolutns.comwrote: Greetings, Today we found out that our Google Apps Open ID related code suddenly stopped working resulting in blocking of all Open ID sign-ins. We use openid4java, the very bottom of the stack trace it shows the real cause: *Caused by: java.lang.NoClassDefFoundError: com/google/apphosting/runtime/security/shared/stub/javax/ net/ssl/SSLContext* * at java.lang.Class.getDeclaredConstructors0(Native Method)* * at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)* * ... 126 more* *Caused by: java.lang.ClassNotFoundException: com.google.apphosting.runtime.security.shared.stub.javax. net.ssl.SSLContext* * at com.google.appengine.runtime.Request.process- ef6eb452cfea3de1(Request.java)* * ... 126 more* This is initiated from guice and openid4java, the root exception is: *Caused by: com.google.inject.internal.ComputationException: com.google.inject.internal.ComputationException: java.lang.SecurityException: Unable to get members for class org.openid4java.util.HttpFetcherFactory* HttpFetcherFactory can be constructed with SSLContext as parameter, I guess something changed in the hosting environment that causes this code to be no longer working. Locally everything works just fine. Any help? This is urgent request, the problem happens on production server currently. Best Regards, --alex -- 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/-/5-gu-**UElC_cJhttps://groups.google.com/d/msg/google-appengine/-/5-gu-UElC_cJ . To post to this group, send email to google-a...@googlegroups.**com. To unsubscribe from this group, send email to google-appengi...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/google-appengine?hl=enhttp://groups.google.com/group/google-appengine?hl=en . -- Takashi Matsuo | Developers Advocate | tma...@google.com -- 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/-/vY9ZJFziZlwJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Takashi Matsuo | Developers Advocate | tma...@google.com javascript: -- 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/-/wuAUegTKeCgJ. 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.
Re: [google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
*Hi All,
Beginning yesterday, September 11, Google App Engine experienced two
periods of serving degradation for a subset of Java applications due to a
gradual roll-out of a new version of the Java runtime. Affected
applications would have seen errors related to class loading. We have
resolved the first issue by fixing the underlying bug. We are still
investigating the cause of the second issue but have rolled back the
problematic update and all affected applications should now be returned to
normal serving behavior.
No changes to your code or application configuration are needed at this
time. We apologize for any inconvenience this issue has caused, and we’ll
follow up with more details on the underlying incident and resolution soon.
Regards,
Christina Ilvento, App Engine PM*
On Wed, Sep 12, 2012 at 1:34 PM, Kaan Soral kaanso...@gmail.com wrote:
I wonder what happened, subscribed to this topic to be updated, hope
someone explains what happened and additionally hope this never happens to
me (python) :)
On Wednesday, September 12, 2012 11:00:49 PM UTC+3, Jeff Schnitzer wrote:
We are back up and running now after 2 hrs of downtime.
To whoever fixed it: THANK YOU!!!
To whoever broke it in the first place: SPANKINGS!!!
Jeff
On Wed, Sep 12, 2012 at 12:11 PM, Jeff Schnitzer je...@infohazard.org
wrote:
More information:
* The failure began at 10:54am (pacific).
* Same app on different appid has the same problem.
(as listed in the stacktraces, the appid is voost0)
Jeff
On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer je...@infohazard.org
wrote:
HELP!
We have tried everything at this point. Shut down instances, tried to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice error
must be a symptom; the smoking gun seems to be:
java.lang.**ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer je...@infohazard.org
wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two days.
All of a sudden (10 mins ago) our app stopped running. Every attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.**GuiceFilter setPipeline: Multiple
Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.**CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization took
514 millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.**jetty.**RuntimeAppEngineWebAppContext@*
*1479784{/,/base/data/home/**apps/s~voost0/2012-09-10-1715.**361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at org.jboss.resteasy.plugins.**providers.RegisterBuiltin.**
register(RegisterBuiltin.java:**35)
at
org.jboss.resteasy.spi.**ResteasyDeployment.start(**ResteasyDeployment.java:211)
at org.jboss.resteasy.plugins.**server.servlet.**
ServletContainerDispatcher.**init(**ServletContainerDispatcher.**java:67)
at org.jboss.resteasy.plugins.**server.servlet.**
FilterDispatcher.init(**FilterDispatcher.java:39)
at st.voo.tick.util.**GuiceResteasyFilterDispatcher.**init(**
GuiceResteasyFilterDispatcher.**java:48)
at
com.google.inject.servlet.**FilterDefinition.init(**FilterDefinition.java:114)
at com.google.inject.servlet.**ManagedFilterPipeline.**
initPipeline(**ManagedFilterPipeline.java:98)
at com.google.inject.servlet.**GuiceFilter.init(GuiceFilter.*
*java:172)
at
org.mortbay.jetty.servlet.**FilterHolder.doStart(**FilterHolder.java:97)
at
org.mortbay.component.**AbstractLifeCycle.start(**AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.**ServletHandler.initialize(**ServletHandler.java:662)
at org.mortbay.jetty.servlet.**Context.startContext(Context.*
*java:140)
at
org.mortbay.jetty.webapp.**WebAppContext.startContext(**WebAppContext.java:1250)
at
org.mortbay.jetty.handler.**ContextHandler.doStart(**ContextHandler.java:517)
at
Re: [google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
This is why I love App Engine, when a problem occurs instead of having a
heart attack or committing suicide, you can just wait for it to be
resolved. I remember downtime's that lasted nearly a day when I was on a
custom server/php platform. App Engine really is a breeze, at the worst
case this happens :)
However new release related bugs are very frequent
On Thursday, September 13, 2012 12:56:28 AM UTC+3, Christina Ilvento wrote:
*Hi All,
Beginning yesterday, September 11, Google App Engine experienced two
periods of serving degradation for a subset of Java applications due to a
gradual roll-out of a new version of the Java runtime. Affected
applications would have seen errors related to class loading. We have
resolved the first issue by fixing the underlying bug. We are still
investigating the cause of the second issue but have rolled back the
problematic update and all affected applications should now be returned to
normal serving behavior.
No changes to your code or application configuration are needed at this
time. We apologize for any inconvenience this issue has caused, and we’ll
follow up with more details on the underlying incident and resolution soon.
Regards,
Christina Ilvento, App Engine PM*
On Wed, Sep 12, 2012 at 1:34 PM, Kaan Soral kaan...@gmail.comjavascript:
wrote:
I wonder what happened, subscribed to this topic to be updated, hope
someone explains what happened and additionally hope this never happens to
me (python) :)
On Wednesday, September 12, 2012 11:00:49 PM UTC+3, Jeff Schnitzer wrote:
We are back up and running now after 2 hrs of downtime.
To whoever fixed it: THANK YOU!!!
To whoever broke it in the first place: SPANKINGS!!!
Jeff
On Wed, Sep 12, 2012 at 12:11 PM, Jeff Schnitzer je...@infohazard.org
wrote:
More information:
* The failure began at 10:54am (pacific).
* Same app on different appid has the same problem.
(as listed in the stacktraces, the appid is voost0)
Jeff
On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer je...@infohazard.org
wrote:
HELP!
We have tried everything at this point. Shut down instances, tried
to
deploy a new version, even tried old versions. We've reported a
production issue. Something is broken inside of GAE. The Guice
error
must be a symptom; the smoking gun seems to be:
java.lang.**ClassNotFoundException: java.io.FileOutputStream
We've been down for 30 mins and getting complaints from our clients.
This looks really, really bad. It's my nightmare scenario - an
outage
in GAE that is small enough not to raise major alarm bells, but
nevertheless cripples my business. It is not the first time this has
happened. It is shaking my faith in GAE.
Jeff
On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer
je...@infohazard.org wrote:
Our app has been running fine on the same version, no code deploys
(our versions are timestamped so this is 100% certain), for two
days.
All of a sudden (10 mins ago) our app stopped running. Every
attempt
to run a request produces this cryptic message:
2012-09-12 10:56:21.791
com.google.inject.servlet.**GuiceFilter setPipeline: Multiple
Servlet
injectors detected. This is a warning indicating that you have more
than one GuiceFilter running in your web application. If this is
deliberate, you may safely ignore this message. If this is NOT
deliberate however, your application may not work as expected.
D 2012-09-12 10:56:21.792
st.voo.tick.util.cambridge.**CambridgeSetup init: Establishing
cambridge view resolver
I 2012-09-12 10:56:21.792
st.voo.tick.GuiceConfig contextInitialized: Guice initialization
took 514 millis
W 2012-09-12 10:56:21.888
Failed startup of context
com.google.apphosting.utils.**jetty.**RuntimeAppEngineWebAppContext@
**1479784{/,/base/data/home/**apps/s~voost0/2012-09-10-1715.**361669184733923098}
java.lang.RuntimeException: java.lang.RuntimeException: Unable to
instantiate MessageBodyReader
at org.jboss.resteasy.plugins.**providers.RegisterBuiltin.**
register(RegisterBuiltin.java:**35)
at
org.jboss.resteasy.spi.**ResteasyDeployment.start(**ResteasyDeployment.java:211)
at org.jboss.resteasy.plugins.**server.servlet.**
ServletContainerDispatcher.**init(**ServletContainerDispatcher.**java:67)
at org.jboss.resteasy.plugins.**server.servlet.**
FilterDispatcher.init(**FilterDispatcher.java:39)
at st.voo.tick.util.**GuiceResteasyFilterDispatcher.**init(*
*GuiceResteasyFilterDispatcher.**java:48)
at
com.google.inject.servlet.**FilterDefinition.init(**FilterDefinition.java:114)
at com.google.inject.servlet.**ManagedFilterPipeline.**
initPipeline(**ManagedFilterPipeline.java:98)
at com.google.inject.servlet.**GuiceFilter.init(GuiceFilter.
**java:172)
Re: [google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
I don't appreciate Google taking down my entire company for 2 hours because they are doing testing in production. We had one customer send out 500 emails today saying hey, check out this site and all they got was an error page. Really poor timing. Last time Google took my entire company down, it was for days, because they decided to block CloudFlare and couldn't just roll back quickly. At least when I was hosting things myself, I had myself to blame... now I just have to hold my breath and hope someone is paying attention and decides to respond at some point in the future. I love the promise of not having to carry a pager, but it is also fear inducing at the same time. Of course I have the option of paying $500/month to have a phone number to call, but that seems kind of outrageous for an issue that looks like it shouldn't have made it to production in the first place. Really, 4+ hours of silence isn't good business. A simple response of 'Hey, we are looking into this, we'll let you know more when we know more' would have been super helpful for my blood pressure. At least I could then respond back to my client saying that I know it is being worked on. Christina, is something like that really out of the question? thanks, jon On Wed, Sep 12, 2012 at 3:12 PM, Kaan Soral kaanso...@gmail.com wrote: This is why I love App Engine, when a problem occurs instead of having a heart attack or committing suicide, you can just wait for it to be resolved. I remember downtime's that lasted nearly a day when I was on a custom server/php platform. App Engine really is a breeze, at the worst case this happens :) However new release related bugs are very frequent On Thursday, September 13, 2012 12:56:28 AM UTC+3, Christina Ilvento wrote: *Hi All, Beginning yesterday, September 11, Google App Engine experienced two periods of serving degradation for a subset of Java applications due to a gradual roll-out of a new version of the Java runtime. Affected applications would have seen errors related to class loading. We have resolved the first issue by fixing the underlying bug. We are still investigating the cause of the second issue but have rolled back the problematic update and all affected applications should now be returned to normal serving behavior. No changes to your code or application configuration are needed at this time. We apologize for any inconvenience this issue has caused, and we’ll follow up with more details on the underlying incident and resolution soon. Regards, Christina Ilvento, App Engine PM* On Wed, Sep 12, 2012 at 1:34 PM, Kaan Soral kaan...@gmail.com wrote: I wonder what happened, subscribed to this topic to be updated, hope someone explains what happened and additionally hope this never happens to me (python) :) On Wednesday, September 12, 2012 11:00:49 PM UTC+3, Jeff Schnitzer wrote: We are back up and running now after 2 hrs of downtime. To whoever fixed it: THANK YOU!!! To whoever broke it in the first place: SPANKINGS!!! Jeff On Wed, Sep 12, 2012 at 12:11 PM, Jeff Schnitzer je...@infohazard.org wrote: More information: * The failure began at 10:54am (pacific). * Same app on different appid has the same problem. (as listed in the stacktraces, the appid is voost0) Jeff On Wed, Sep 12, 2012 at 11:53 AM, Jeff Schnitzer je...@infohazard.org wrote: HELP! We have tried everything at this point. Shut down instances, tried to deploy a new version, even tried old versions. We've reported a production issue. Something is broken inside of GAE. The Guice error must be a symptom; the smoking gun seems to be: java.lang.**ClassNotFoundExcepti**on: java.io.FileOutputStream We've been down for 30 mins and getting complaints from our clients. This looks really, really bad. It's my nightmare scenario - an outage in GAE that is small enough not to raise major alarm bells, but nevertheless cripples my business. It is not the first time this has happened. It is shaking my faith in GAE. Jeff On Wed, Sep 12, 2012 at 11:11 AM, Jeff Schnitzer je...@infohazard.org wrote: Our app has been running fine on the same version, no code deploys (our versions are timestamped so this is 100% certain), for two days. All of a sudden (10 mins ago) our app stopped running. Every attempt to run a request produces this cryptic message: 2012-09-12 10:56:21.791 com.google.inject.servlet.**Guic**eFilter setPipeline: Multiple Servlet injectors detected. This is a warning indicating that you have more than one GuiceFilter running in your web application. If this is deliberate, you may safely ignore this message. If this is NOT deliberate however, your application may not work as expected. D 2012-09-12 10:56:21.792 st.voo.tick.util.cambridge.**Cam**bridgeSetup init: Establishing cambridge view resolver I 2012-09-12 10:56:21.792 st.voo.tick.GuiceConfig
Re: [google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
On Wed, Sep 12, 2012 at 3:12 PM, Kaan Soral kaanso...@gmail.com wrote: This is why I love App Engine, when a problem occurs instead of having a heart attack or committing suicide, you can just wait for it to be resolved. Hmmm. This really unfortunately timed incident may have cost us an important client, so I'm not feeling the love. I have quite a lot of experience building and running large online systems prior to embracing GAE and my products have never had as much downtime as I've had over the last year. It hasn't always been Google's fault (the entire .st registry going down for 8+ hours really sucked[1]) but it usually has been. See: * Instance startup time ballooning by 3X and hitting deadlines (multiple occasions) * GAE blocking CloudFlare with an undocumented security system * This incident, where Java instances started mysteriously failing Would waiting have fixed these issues? I'm not convinced. Google may have smart people running GAE but they aren't watching _my_ app, they're just watching for an uptick in the number of complaints. If you're doing something slightly unusual (say, running a CF reverse proxy), you might be statistical noise. Apparently this Java problem _was_ widespread, but I had no way of knowing that. GAE's value proposition is that it's better to have Google's smart engineers building and maintaining your infrastructure. But my site would be more reliable if I had one dumb person (possibly me) who cares specifically about _my_ infrastructure. I've screwed up deployments and upgrades in production before, but at least I'm aware when changes happen, get immediate feedback, and can fix the problem right then and there. With GAE, the only thing I can do when my alarms go off is to whine as loudly as possible. But there is no feedback! I have no way of knowing if Google is working on the problem or if they're still waiting for more complaints that will never materialize. Will I be down for 15 minutes, 1 hour, 2 hours, 8 hours, forever? How long do you want to wait? This feels like a fundamental flaw in the PaaS concept, destined to produce multiple-hour downtimes at irregular intervals. The feedback loop is too slow (and lossy if the problem is not widespread). There's no amount of QA or testing that will prevent failures in a system as big as complicated as GAE. So the only reasonable option is to get that feedback loop shorter. How can that happen? Some ideas: * Google could announce when they are rolling out changes. I don't need release notes (although it would be nice to know what to watch for) but I'd like to know when I should pay extra attention. Or not schedule client demos. Facebook does something like this, rolling out platform changes on specific days of the week (which I long ago stopped caring about). * Google could make extra support channels available during this time. Hell, use twitter. Think of us as your QA staff - if we see something amiss, we'd like to let you know. * Google could be more transparent about problems as they happen. When you know there is an issue, let us know. Since I must assume that any problem which Google hasn't acknowledged is a problem Google doesn't know about, I can stop spamming @google.com addresses. * Google could monitor our apps, and compare error rates before rollout to error rates after rollout. Ideally you'd break this down by component; figure out which apps use the search api, so when you roll out changes to the search system, you're specifically watching for an uptick in 500 errors from those apps. Something like that. Any other ideas? I really like GAE and I really like the PaaS concept. But reliability is really a problem. It's probably going to be an even bigger problem going on into the future as GAE (hopefully) adds new features and gets a bigger footprint. More moving parts means more failures. Jeff P.S. Paying $6k/yr for Premier Support is not the answer. Whether or not that would solve my problem, that doesn't solve GAE's problem. [1]: http://blorn.com/post/29851770158/beware-cutesy-two-letter-tlds-for-your-domain-name -- 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-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] App deployment stuck and then failed with version not ready
I am unable to deploy to my apps in the past 20 hrs. All deployments stuck at the stage of Verifying availability of frontend and eventually failed with Version not ready. My AppIDs are aos-prod-1 aos-prod-2. Any help will be greatly appreciated! -- 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/-/7Hs6RaPSM74J. 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.
Re: [google-appengine] Re: APP DOWN: App suddenly no longer starts, no code changes
Hi Jeff, I feel sorry for your loss. I agree completely with your message and your recommendation to Google. Hi GAE team, at the very least, please let us know when you want to roll out upgrades and stuff. It might not break stuff, but we need to know so we can be prepared (at least we won't send newsletter to thousands of people, Hey check our website now or schedule a pitch to investor). On Thursday, 13 September 2012 08:35:39 UTC+8, Jeff Schnitzer wrote: On Wed, Sep 12, 2012 at 3:12 PM, Kaan Soral kaan...@gmail.comjavascript: wrote: This is why I love App Engine, when a problem occurs instead of having a heart attack or committing suicide, you can just wait for it to be resolved. Hmmm. This really unfortunately timed incident may have cost us an important client, so I'm not feeling the love. I have quite a lot of experience building and running large online systems prior to embracing GAE and my products have never had as much downtime as I've had over the last year. It hasn't always been Google's fault (the entire .st registry going down for 8+ hours really sucked[1]) but it usually has been. See: * Instance startup time ballooning by 3X and hitting deadlines (multiple occasions) * GAE blocking CloudFlare with an undocumented security system * This incident, where Java instances started mysteriously failing Would waiting have fixed these issues? I'm not convinced. Google may have smart people running GAE but they aren't watching _my_ app, they're just watching for an uptick in the number of complaints. If you're doing something slightly unusual (say, running a CF reverse proxy), you might be statistical noise. Apparently this Java problem _was_ widespread, but I had no way of knowing that. GAE's value proposition is that it's better to have Google's smart engineers building and maintaining your infrastructure. But my site would be more reliable if I had one dumb person (possibly me) who cares specifically about _my_ infrastructure. I've screwed up deployments and upgrades in production before, but at least I'm aware when changes happen, get immediate feedback, and can fix the problem right then and there. With GAE, the only thing I can do when my alarms go off is to whine as loudly as possible. But there is no feedback! I have no way of knowing if Google is working on the problem or if they're still waiting for more complaints that will never materialize. Will I be down for 15 minutes, 1 hour, 2 hours, 8 hours, forever? How long do you want to wait? This feels like a fundamental flaw in the PaaS concept, destined to produce multiple-hour downtimes at irregular intervals. The feedback loop is too slow (and lossy if the problem is not widespread). There's no amount of QA or testing that will prevent failures in a system as big as complicated as GAE. So the only reasonable option is to get that feedback loop shorter. How can that happen? Some ideas: * Google could announce when they are rolling out changes. I don't need release notes (although it would be nice to know what to watch for) but I'd like to know when I should pay extra attention. Or not schedule client demos. Facebook does something like this, rolling out platform changes on specific days of the week (which I long ago stopped caring about). * Google could make extra support channels available during this time. Hell, use twitter. Think of us as your QA staff - if we see something amiss, we'd like to let you know. * Google could be more transparent about problems as they happen. When you know there is an issue, let us know. Since I must assume that any problem which Google hasn't acknowledged is a problem Google doesn't know about, I can stop spamming @google.com addresses. * Google could monitor our apps, and compare error rates before rollout to error rates after rollout. Ideally you'd break this down by component; figure out which apps use the search api, so when you roll out changes to the search system, you're specifically watching for an uptick in 500 errors from those apps. Something like that. Any other ideas? I really like GAE and I really like the PaaS concept. But reliability is really a problem. It's probably going to be an even bigger problem going on into the future as GAE (hopefully) adds new features and gets a bigger footprint. More moving parts means more failures. Jeff P.S. Paying $6k/yr for Premier Support is not the answer. Whether or not that would solve my problem, that doesn't solve GAE's problem. [1]: http://blorn.com/post/29851770158/beware-cutesy-two-letter-tlds-for-your-domain-name -- 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/-/OsO531fxrSAJ. To post to this group,
