https://bz.apache.org/bugzilla/show_bug.cgi?id=66120
--- Comment #5 from Mark Thomas <ma...@apache.org> --- Having started work on this it is more complex that it first appears. The main reason is needing to make sure a cluster can perform a rolling upgrade. Getting this to work in a Tribes based cluster requires creating a new message type. Currently, receiving a new message type will trigger an error. This means users need to upgrade in two stages. First to a version that understands (or at least doesn't trigger an error) for the new message type. Second to a version that uses the new message type to transfer the session note. We may decide to wait more than one release from implementing the first stage to the second. The fix for non-cluster managers (which is what the original request was for) looks to be simpler and should be possible to provide in the next release. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
