Bug 1088791 - [GSS] (6.2.x) Timed out conversation unexpectedly alive on next request
Summary: [GSS] (6.2.x) Timed out conversation unexpectedly alive on next request
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CDI/Weld
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR3
: EAP 6.2.3
Assignee: Martin Kouba
QA Contact: Ron Šmeral
Russell Dickenson
URL:
Whiteboard:
Depends On: 1070069
Blocks: eap62-cp03-blockers 1089989 1095141
TreeView+ depends on / blocked
 
Reported: 2014-04-17 08:02 UTC by Carlo de Wolf
Modified: 2018-12-05 18:13 UTC (History)
11 users (show)

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.
Clone Of: 1070069
Environment:
Last Closed: 2014-06-09 12:47:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WELD-1452 0 Major Resolved Conversation timeout in redirect 2016-08-12 07:44:22 UTC
Red Hat Issue Tracker WELD-1657 0 Major Resolved Backport WELD-1452 2016-08-12 07:44:22 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.