I don't know if anyone else has spotted this, and it may well be the case for 
other servlet containers as well, but we noticed that objects were being 
propagated across our cluster even when a page that only read the session 
object was just being refreshed.

This is a very serious issue, not quite a blocker because everything functions 
okay, but I really think this should be fixed and released as 5.1.0.6 as soon 
as possible. Please take a look at the bug and vote for it if you agree: 
https://issues.apache.org/jira/browse/TAP5-834

I've included a couple of suggestions of solutions, please comment if you thing 
there are any drawbacks or better ones.

Thanks,

Andy.

Reply via email to