What you are seeing is normal JEE behavior with cluster environments. The standard does not say that modifications to your session-stored beans should be propagated to other cluster nodes unless you explicitely invoke setAttribute().
You are experiencing the worst possible case (never increments) because GAE always serializes your sessions to memcache between requests. With any other app server in cluster you would get undefined behavior (only increments as long as there is no node failure). I would recommend to use memcache counters for this purpose, using the session ID (or maybe the user ID) as key. On Apr 19, 2:12 pm, Thomas <[email protected]> wrote: > I have submitted the > issue#3112.http://code.google.com/p/googleappengine/issues/detail?id=3112 > > -- > 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. -- 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.
