There's no guarantee that both those threads are running on the same instance. They can be on two different machines in two different data centers.
On Fri, May 13, 2011 at 5:22 AM, Samuel Erdtman <[email protected]> wrote: > Hi > I have created an application that works fin in the eclipse app engine > development environment but when I deploy it live I get some problems. > > My application depends on two request coming in simultaneously from two > different browsers, both requests (threads) gets a map from servlet context > then both gets an object from the map with the same key, i.e. the same > object super.toString says so and .hashCode says so. > The first thread updates the object and then waits for the other thread to > signal that it has read the change and done some operations. But the second > thread never sees the change made by the first thread, the result of this is > thet the first thread hanging for 30 seconds and the throws an exception. > > If I let the first thread return the second thread sees the change, but > then it is too late. > > The project is up and running but not working at > http://sendnow4.appspot.com and the code (not the latest but a working > version) can be found at http://code.google.com/p/sendnow/ > > Best regards > //Samuel > > -- > 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. > -- 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.
