who does keep the websessions? Can't you see that in your profiler?
we don't hold reference to the object itself anywhere in the code except
when handling a request itself.
johan
On 5/22/07, -Vlad- <[EMAIL PROTECTED]> wrote:
Hi,all.
I've just noted the fact that after the session timeout time there is a
call
to the MyWebApplication.sessionDestroyed(String sessionId) method, as it
is
supposed to be.
This method removes data from responce buffer, and that is all.
WebSession object remains in the JVM heap(Tested by means of JProfiler).
And
the number of these objects grows as users' http sessions expire. How can
I
remove all references to the wicket's webSession object when it expires?
--
View this message in context:
http://www.nabble.com/Problem-with-wicket%27s-WebSession-objects.-Memory-leakage--tf3796071.html#a10736960
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
-------------------------------------------------------------------------
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
