[TRINIDAD-1858] Fix fail-over bugs where session state is mutated without dirtying the Session objects

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.13-core , 2.0.0-beta-1
• Fix Version/s: 1.2.14-core , 2.0.0-beta-1
• Assignee: Blake Sullivan
• Reporter: Blake Sullivan
• Created: 16/Jul/10 22:23
• Updated: 13/Jan/11 11:56
• Resolved: 28/Oct/10 00:51

Description

In order for servlet engines to know which Session attributes to fail over at the end of the request, the Session tracks which attributes have had puts or removes performed on them. This means that in order to be failed over, any change to an object tree rooted in a Session attribute must dirty the session attribute by the end of the request. There are bugs in both the TokenCache and SessionChangeManager where they don't do this in all cases