Nacho, I don't want to argue either side, but there are some gray areas: in this case, the feature that we tried to use wasn't supported, but I don't believe that it is clearly documented, nor the behavior of the APIs and the web interface were exactly helpful for developers.
Whatever the application does, ideally it should not lead to the admin console crashing with HTTP 500 error code. If it is crashes, it is clearly a bug on GAE side - but is it critical/blocking, if we know what caused it to be surfaced and we know alternate approach? Definitely no. The same is about exception APIs returned when we tried to query those objects from the DB: was the exception very helpful? No. But thanks to Jason from Google, we found out the reason for the exception and worked around, so our problem was solved although of course again - not informative exception is a bug in API (just as the fact that some objects can be stored but not retrieved), and ideally it should be fixed in future, but it's not blocking to us. My point is, there are bugs on GAE side, but I don't have expectations that all of them will be fixed - I hope just that those which cannot be reasonably worked around, will be fixed :) On Thu, Nov 19, 2009 at 1:20 AM, Nacho Coloma <[email protected]> wrote: > Diana, I cannot talk for Google but I suppose you cannot _require_ as > an obligation that Google fixes your own bugs. > > If Dimitry is able to identify a bug in GAE, he should point it out > and the GAE folks will address it. Other than that, you are subject to > a "bona fide" effort, which may not be what you are looking for. In > that case, you should look for paid support (there are third parties > that offer such services). > > Just a heads up. > > Nacho (not from Google) > > On Nov 19, 8:35 am, Diana Cruise <[email protected]> wrote: >> Excellent news. How long did it take to resolve this matter and what >> was the impact to your Users? >> >> I assume you would agree we could avoid this type of problem by only >> using the data types listed here right? >> >> http://code.google.com/appengine/docs/java/datastore/dataclasses.html... >> >> On Nov 18, 3:27 pm, Dmitry Anipko <[email protected]> wrote: >> >> > Thanks Jason for help. In our case the problem was caused by usage of >> > byte[] field in a persisted class. Somehow though, it wasn't causing >> > any problems immediately, but only after a few objects have been >> > saved. Per Jason, usage of byte[] in JDO on GAE isn't supported. >> >> > On Wed, Nov 18, 2009 at 1:00 PM, Diana Cruise <[email protected]> >> > wrote: >> > > What's the latest here Dmitry...can GAE handle more than 100 request >> > > or not? Please update where you are with this problem. Thanks. >> >> > > On Nov 9, 5:15 pm, Dmitry Anipko <[email protected]> wrote: >> > >> Following up offline and will update with resolution later. >> >> > >> On Mon, Nov 9, 2009 at 9:50 AM, Jason (Google) <[email protected]> >> > >> wrote: >> > >> > As always, I need your application ID in order to help troubleshoot >> > >> > app-specific issues. Please provide that and any stack traces or >> > >> > other error >> > >> > messages you see in your application's logs. >> >> > >> > - Jason >> >> > >> > On Fri, Nov 6, 2009 at 9:47 PM, Dmitry Anipko >> > >> > <[email protected]> >> > >> > wrote: >> >> > >> >> After some more experimentation, it looks like there is something in >> > >> >> the data store that is surfaced by our application: >> >> > >> >> if I clean up the store for the application completely, using the web >> > >> >> interface, then for the first ~100 request it works fine, but after >> > >> >> some time, it starts producing those errors I wrote before - it can't >> > >> >> query objects by index (and that problem persists until I clean the >> > >> >> store again). >> >> > >> >> The second observation - although I don't know if it is related or >> > >> >> not >> > >> >> - is when the store for my app is in such state, and I try to view >> > >> >> objects through the web interface, the web interfaces crashes with >> > >> >> the >> > >> >> error 500: >> >> > >> >> Server Error >> > >> >> A server error has occurred. >> >> > >> >> Return to Applications screen » >> >> > >> >> GAE folks, can someone please take a look - this is a blocking issue >> > >> >> for my team, and I don't know how to proceed here without your help. >> >> > >> >> Everything works just fine when I run it on a local development >> > >> >> server. >> >> > >> >> Thank you. >> >> > >> >> On Nov 6, 11:05 am, Diana Cruise <[email protected]> wrote: >> > >> >> > I see NO reply from GAE here regarding such a critical issue!!! >> >> > >> >> > Is your app still down, what is the status of your app? How are we >> > >> >> > supposed to put an application in production with GAE if such a >> > >> >> > problem can occur with NO response for 3 days? Is there another >> > >> >> > channel to raise such high-priority issues to get proper helpdesk >> > >> >> > response? >> >> > >> >> > On Nov 4, 1:58 am, Dmitry Anipko <[email protected]> wrote: >> >> > >> >> > > It is 11:56 Pacific 11/3/2009, are there any known issues withGAE >> > >> >> > > right now? >> >> > >> >> > > My application that has been working for a couple of months now >> > >> >> > > today >> > >> >> > > started producing failures for some queries from the data store >> > >> >> > > (basically an object which has just been stored cannot be >> > >> >> > > retrieved >> > >> >> > > after that by key), and after some time started producing even >> >> > >> >> > > <html><head> >> > >> >> > > <meta http-equiv="content-type" >> > >> >> > > content="text/html;charset=utf-8"> >> > >> >> > > <title>500 Server Error</title> >> > >> >> > > </head> >> > >> >> > > <body text=#000000 bgcolor=#ffffff> >> > >> >> > > <h1>Error: Server Error</h1> >> > >> >> > > <h2>The server encountered an error and could not complete your >> > >> >> > > request.<p>If the problem persists, please <A HREF="http:// >> > >> >> > > code.google.com/appengine/support/">report</A> your problem and >> > >> >> > > mention this error message and the query that caused it.</h2> >> > >> >> > > <h2></h2> >> > >> >> > > </body></html> >> >> > >> >> > > The same application executes just fine in the >> > >> >> > > localGAEdevelopment >> > >> >> > > environment. Can folks fromGAEcomment if there is any maintenance >> > >> >> > > going on right now or how could I get more details on what >> > >> >> > > causing the >> > >> >> > > failures (again the same code worked for quite some time now, so >> > >> >> > > I >> > >> >> > > think it is unlikely the code is the issue here). Thanks for your >> > >> >> > > help.- Hide quoted text - >> >> > >> >> > - Show quoted text -- Hide quoted text - >> >> > >> - Show quoted text - >> >> > > -- >> >> > > You received this message because you are subscribed to the Google >> > > Groups "Google App Engine for Java" group. >> > > To post to this group, send email to >> > > [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected]. >> > > For more options, visit this group >> > > athttp://groups.google.com/group/google-appengine-java?hl=en.-Hide >> > > quoted text - >> >> > - Show quoted text - > > -- > > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=.
