Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6751

Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0
    • Fix Version/s: EAP_EWP 5.1.2 ER1
    • Component/s: Seam
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1) Deploy seam numberguess application.
      2) Access to http://host:port/seam-numberguess/.
      3) The above two objects are not removed, when conversationTimeout occurs.

      Show
      1) Deploy seam numberguess application. 2) Access to http://host:port/seam-numberguess/ . 3) The above two objects are not removed, when conversationTimeout occurs.
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      1) Download attached ConversationTimeoutWorkaround.java
      2) Compile ConversationTimeoutWorkaround.java
      3) Add the compiled class file to jboss-seam-numberguess.ear/jboss-seam-numberguess.jar

      Show
      1) Download attached ConversationTimeoutWorkaround.java 2) Compile ConversationTimeoutWorkaround.java 3) Add the compiled class file to jboss-seam-numberguess.ear/jboss-seam-numberguess.jar
    • Release Notes Text:
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  ksato Keiichi Sato
                  Writer:
                  Russell Dickenson
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: