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.
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
Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only
Verified in EAP 6.3.0.ER4.