timezone differences between clients make for funny invalidation (in sessions,
ehcache, etc)
--------------------------------------------------------------------------------------------
Key: CDV-905
URL: https://jira.terracotta.org/jira//browse/CDV-905
Project: Community Development
Issue Type: New Feature
Reporter: Tim Eck
Assignee: Issue Review Board
I've debugged this a few times now in various customer contexts that it seems
we could do something a little more proactive about it at some point. When the
timezone is different between two L1s, it can make for an immediate time jump
that instantly causes sessions to become invalid.
Seems like we could store the local timezone setting along with a roots in this
case and at least produce a warning when a discrepency is noticed (ie. the
timezone of the node faulting the root is different from the timezone of the VM
that first created it). Doing something similar but at the level of each
session would work too, but I can't see any advantage to storing timezone info
for every session
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
