-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.0
-
None
-
-
Release Notes
-
Workaround Exists
-
-
The ServerConversationContext.flush() method created in some cases PersistentContext and BusinessContext instances and these instances lived in memory until the HTTP Session was invalidated. This problem is solved by creating them only when required.
-
Documented as Resolved Issue
-
NEW
Platform JIRA for JBSEAM-4819.
The following two objects are leaked, when conversationTimeout occurs.
org.jboss.seam.bpm.businessProcess
org.jboss.seam.persistence.persistenceContexts
This is not a permanent leak, because if associated HTTP session is invalidated, the above objects are removed.
The object size of the leaked objects are very small,
so this is not a serious memory leak issue.
This can be easily reproduced with the seam numberguess application.
- clones
-
JBPAPP-6842 Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs
- Closed