Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-636

Weld doesn't handle LRC properly when HttpSession is timeout or invalidate

    XMLWordPrintable

Details

    Description

      See http://seamframework.org/Community/BugAboutTheConversationScope#comment136758 for detail,
      This is related with ticket https://jira.jboss.org/browse/WELD-587

      To Summary the problem:
      1> If user call Session.invalidate() or HttpSession is timeout with a LRC exist, when redirect and get, the Weld can't restore the conversation specified with request parameter: "?cid=1", and will generate an Exception:
      SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
      org.jboss.weld.context.NonexistentConversationException: WELD-000301 Could not restore long-running conversation 1 because id not known

      2> If user's HttpSession is timeout when there is a LRC exists, the @PreDestroy method of @ConversationScoped beans didn't be called.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WELD-587 Exception happened when invalid session before ending Conversation with Post-Redirect-Get

          • 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

              pmuiratbleepbleep Pete Muir (Inactive)
              wangliyu_jira Wang Liyu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: