Sorry, the reason of memory leak is not the Orchestra. The incorrect configuration of second level Hibernate cache is the reason: i use it to cache the entities with composite id. Such a composite id keeps the references to a huge object tree.
alsha wrote: > > 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-tp22057577p22083814.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
