Hi *, I've noticed, that ConversationManager is simply removed from ConversationWiperThread (in ConversationManagerSessionListener), when http session is expired (or invalidated). So, PersistenceContextCloser.valueUnbound(ConversationBindingEvent event) is NOT invoked in this case and has no chance to close persistent context (Hibernate session in my case). Conversation timeout works correct, in opposite. I think that this is the reason for memory leak in my application. Is it a desired behaviour or a bug?
Thanks a lot, Alexey -- View this message in context: http://www.nabble.com/-ORCHESTRA--Possible-memory-leak-during-htpp-session-timeout-invalidation-tp22057577p22057577.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
