Weld doesn't handle LRC properly when HttpSession is timeout or invalidate
--------------------------------------------------------------------------
Key: WELD-636
URL: https://jira.jboss.org/browse/WELD-636
Project: Weld
Issue Type: Bug
Components: Conversations, Web Tier integration (JSF, JSP, EL and
Servlet)
Affects Versions: 1.1.0.BETA2
Environment: Tomcat6/GF3.0.1/JBoss6M4 with Weld1.1.0-SNAPSHOT
Reporter: Wang Liyu
Priority: Critical
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
