Bug 1088791

Summary: [GSS] (6.2.x) Timed out conversation unexpectedly alive on next request
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Carlo de Wolf <cdewolf>
Component: CDI/WeldAssignee: Martin Kouba <mkouba>
Status: CLOSED CURRENTRELEASE QA Contact: Ron Šmeral <rsmeral>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.1.0CC: amelicha, bmaxwell, cdewolf, jawilson, jharting, ksato, maschmid, myarboro, pmuir, rsvoboda, tkimura
Target Milestone: CR3   
Target Release: EAP 6.2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In a JSF application, a conversation was unexpectedly activated and associated with a request even after the conversation had expired, resulting in a 'NonExistentConversationException' error. The root cause of this issue was that Weld did not properly check the state of conversation when initiating requests. To resolve this issue the conversation context activation and invalidation procedure has been amended to check conversation state more thoroughly. As a result, expired conversations are no longer mistakenly associated with requests.
 Story Points: ---
Clone Of: 1070069 Environment:
Last Closed: 2014-06-09 12:47:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1070069    
Bug Blocks: 1067532, 1089989, 1095141    

Description Carlo de Wolf 2014-04-17 08:02:47 UTC 
+++ This bug was initially created as a clone of Bug #1070069 +++

In JSF app, Weld only checks conversation timeout at the RENDER_RESPONSE phase or respose complete. It doesn't check the conversation at the beginning of requests.

Upstream JIRA is:

Conversation timeout in redirect
https://issues.jboss.org/browse/WELD-1452
Comment 6 Ron Šmeral 2014-05-16 12:18:57 UTC 
Verified in EAP 6.2.3.CP.CR3.