Thanks for the help, Johan. I know that you stores wicket session in HttpSession(as atribute), provided by container. JProfiler shows that some PageMap keeps this. I've tried to get the root of reference chain but failed due to constant JProfiler error. Can it be possible that some pagemap instance is stored not in the wicket Session? I have my custom transient object in wicket session, it is detached and attached when the corresponing methods of the session is called. This object contains some components(extends Component) and models(extends Model), which I use on different pages (Is it a good practice?).
And I also mentioned that 'sessionDestroyed' method doesn't involve calling to 'session.invalidate()' method! But... I've overriden SessionStore, and I call session.invalidate() forcedly when my SessionStore.onUnbind(String sessionId) method is invoked. After that session is GC-ed. But I don't understand why? -- View this message in context: http://www.nabble.com/Problem-with-wicket%27s-WebSession-objects.-Memory-leakage--tf3796071.html#a10739385 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
