Bug 1070069 – [GSS] (6.3.0) Timed out conversation unexpectedly alive on next request

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1070069 - [GSS] (6.3.0) Timed out conversation unexpectedly alive on next request

Summary:	[GSS] (6.3.0) Timed out conversation unexpectedly alive on next request

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	CDI/Weld (Show other bugs)
Sub Component:
Version:	6.1.0,6.2.0,6.1.1,6.2.1,6.2.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER4
Target Release:	EAP 6.3.0
Assigned To:	Jozef Hartinger
QA Contact:	Ron Šmeral
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1088791 1089990
	Show dependency tree / graph

Reported:	2014-02-26 03:10 EST by Takayoshi Kimura
Modified:	2016-10-31 21:37 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP 6 it was found that a conversation could be unexpectedly activated and associated with a request even after the conversation expires, resulting in a `NonExistentConversationException`. This was because, in a JSF application, Weld did not properly check conversation state at the beginning of requests. This release of the product includes an updated conversation context activation and invalidation procedure to check conversation state more thoroughly. As a result, expired conversations no longer get mistakenly associated with requests.
Story Points:	---
Clone Of:
Clones:	1088791 (view as bug list)
Environment:
Last Closed:	2014-06-28 11:40:15 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WELD-1452	Major	Resolved	Conversation timeout in redirect	2016-08-12 03:44 EDT
JBoss Issue Tracker	WELD-1657	Major	Resolved	Backport WELD-1452	2016-08-12 03:44 EDT

Groups: None (edit)

Description Takayoshi Kimura 2014-02-26 03:10:25 EST

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 2 Kabir Khan 2014-04-25 11:14:38 EDT

Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only

Comment 3 Ron Šmeral 2014-05-14 08:51:06 EDT

Verified in EAP 6.3.0.ER4.

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