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

Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • TBD EAP 4
    • 4.3.0.GA_CP09
    • Seam2
    • None
    • 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.
    • Workaround Exists
    • 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
    • Hide
      It was discovered that the <methodname>ServerConversationContext.flush()</methodname> method created unnecessary PersistentContext and BusinessContext instances which remained in memory until the HTTP Session was invalidated. In some cases this caused a minor memory leak. The memory leak issue is now fixed by adding a condition to the method which creates PersistentContext and BusinessContext instances only when needed. This functionality fixes the memory leak issue.
      Show
      It was discovered that the <methodname>ServerConversationContext.flush()</methodname> method created unnecessary PersistentContext and BusinessContext instances which remained in memory until the HTTP Session was invalidated. In some cases this caused a minor memory leak. The memory leak issue is now fixed by adding a condition to the method which creates PersistentContext and BusinessContext instances only when needed. This functionality fixes the memory leak issue.
    • Documented as Resolved Issue
    • ON_QA

    Description

      Backport of JBPAPP-6751.

      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.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-6751 Seam businessProcess and persistenceContexts are leaked when conversationTimeout occurs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mnovotny@redhat.com Marek Novotny
              ksato_jira Keiichi Sato (Inactive)
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: