I'm a bit surprised all the XHR requests are going in parallel, since most browsers limit the amount of XHR calls you can make simultaneously. At any rate, they don't have to be "synchronous", so to speak - you can just chain the callbacks so it doesn't block your UI loading. Hooray for languages where functions are first class objects!
On Wed, Feb 10, 2010 at 1:52 PM, Spines <[email protected]> wrote: > Great! I can definitely initialize synchronously. I was just worried > that there may be an issue with my code that would only show up > sporadically on the production app engine. > > On Feb 10, 1:35 pm, Don Schwarz <[email protected]> wrote: > > On Wed, Feb 10, 2010 at 3:09 PM, Spines <[email protected]> wrote: > > > I get a deadlock on the development server. It happens about once > > > every 4 times I startup my app. It happens at PMF.<clinit>:11 the > > > first time I access my PMF class, which is just a copy paste of the > > > example PMF class from > > >http://code.google.com/appengine/docs/java/datastore/overview.html. > > > Deeper down the call tree I can see that it is hung at > > > Class.getDeclaredConstructors0. > > > > > We fixed this bug recently but it did not make it into the upcoming > 1.3.1 > > > > release. It should be fixed in the next release after that. > > > > > What my app does is: upon loading of the home page, it simultaneously > > > sends 5 jquery requests to the app. Each request takes about a second > > > or two because it initializes a different thing, such as getting the > > > PMF, or loading Spring, etc. > > > > > I'm not sure if it would also deadlock on the production app engine. > > > > No, this deadlock is limited to the DevAppServer. > > > > > Does anyone know what could cause this? Is the development server not > > > meant to handle multiple simultaneous requests? Could this also be a > > > potential situation on the production server? > > > > > Note: When I do all of the initializations synchronously instead of > > > sending out requests simultaneously, everything works fine. > > > > > That makes sense. Can you use that as a workaround until 1.3.2 is > > > > released? > > > > Feel free to file a bug in the issue tracker. We'll update it when the > fix > > is rolled out. > > > > Thanks, > > Don > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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=en.
