This content has been marked as final.
Show 1 reply
-
1. Re: Session Object got stuck in the memory after called HttpSession.invalidate()
wangliyu Aug 4, 2011 11:54 AM (in response to wangliyu)I'm not sure if anyone else has this problem? for a typical web app, you want to release the session/conversation/request beans when user logout, the easiest way is to call HttpSession.invalidate(), but I found it sometime there is always a session instances stuck in the memory.
I'm wondering if this is right way to release the beans or should I use something else to release the object?
I also found that if I call HttpSession.invalidate() at Phase 5 - INVOKE APP, it always stuck, if I call in pre-RENDER phase listener normally it will release, but sometime if the ViewExpired exception happened, it will stuck there.
I think this is a major problem or bug. Could anyone from Weld Team clarify this for me?