Status Update
No update yet.
Comments
va...@google.com
ku...@google.com
Hello,
Thank you for contacting the Google Cloud support team.
I have gone through your reported issue, however it seems like this is an issue observed specifically at your end within your project environment. It would need more specific debugging and analysis. To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system. I'm going to close this issue which will no longer be monitored. If you have any additional issues or concerns, please don’t hesitate to create a new issue on the
Thank you, we appreciate your cooperation!
Description
We've been investigating some inconsistent behavior with part of our application that works with session data. We're at the point where we suspect there might be an issue with how session data is handled within the GAE platform so we're looking for any possible insights into what might be going on.
As a bit of background, within our application users have the ability to manage different sets of configurations. Within each users' session we store the current configuration id along with a list of other configurations they have access to. What we've been seeing is that sometimes when a user selects a different configuration, which we store as the current configuration id in their session, when we later go to retrieve the current configuration id from the session the prior configuration id is returned. When this happens we can check the session data within Cloud Console Memcache and Datastore viewers and see that in fact the configuration id has not been updated.[1] Within the logs there is no indication as to any sort of error or failure taking place.
What you expected to happen:
Calls to HttpSession#setAttribute[2] should always result in the value being updated.
Steps to reproduce:
Frustratingly, it is not possible to reproduce this issue on demand. Sometime the session data fails to update immediately other times it can take dozens of attempts before doing so.
Other information (workarounds you have tried, documentation consulted, etc):
We have experimented with async-session-persistence and have not seen any difference in behavior.
------
[1] According to the <sessions-enabled> section of the App Engine documentation "App Engine includes an implementation of sessions, using the servlet session interface. The implementation stores session data in Datastore for persistence, and also uses memcache for speed."
[2]