I am running a simple web application launched from maven using "jetty-maven-plugin". The simple web application has a Filter which does this;
1) Copies the HttpSession's attributes to a Map
2) Serializes the Map
3) Deserializes the Map
4) Copies the entries of the Map back into HttpSession
In each case, the ClassLoader should be the same (no stranded singletons etc...) and there is no "hot deploy" happening. The purpose of this undertaking is to ensure that the application is able to handle serialized sessions. In doing this experiment, I have observed a memory exhaustion issue around serializing and de-serializing ObjectContext. If I explicitly stop serializing "ObjectContext" then the problem stops.
Using jprofiler, I have observed that the memory consumption increases roughly exponentially in relation to the number of serialization/de-serialization events. Also from jquery analysis I see the memory is being referenced from;
The problem manifests itself quite quickly; a few dozen serialize + de-serialize phases.