HTTP Session Size for clustering



Hi all,

by analyzing the HTTP Flex Session content, I noticed it contains a reference to the message broker, and so to each destination declared (which are Spring business services). The session can then get to several megabytes in size. I could not find if the message broker was correctly dereferenced before the session was serialized. Has anyone some hints about that?