[jboss-jira] [JBoss JIRA] (WFLY-7651) Session invalidation not reflected when coming from another concurrent request

[Guillermo González de Agüero (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillermo González de Agüero updated WFLY-7651:
-----------------------------------------------
    Description: 
When a request is being processed, and another concurrent request invalidates the session, invalidation is not reflected in the first request, i.e.: calling HttpServletRequest#isRequestedSessionIdValid() returns true. But trying to get any request attribute shows that the request is effectively destroyed. The same happens when the session expires after initiating the request.

Related to WFLY-7568 and probably also to WFLY-6744

  was:
When a request is being processed, and another concurrent request invalidates the session, invalidation is not reflected in the first request, i.e.: calling HttpServletRequest#isRequestedSessionIdValid() returns true. But trying to get any request attribute shows that the request is effectively destroyed.

Related to WFLY-7568 and probably also to WFLY-6744



> Session invalidation not reflected when coming from another concurrent request
> ------------------------------------------------------------------------------
>
>                 Key: WFLY-7651
>                 URL: https://issues.jboss.org/browse/WFLY-7651
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.1.0.Final
>            Reporter: Guillermo González de Agüero
>            Assignee: Stuart Douglas
>         Attachments: session-invalidation-1.0-SNAPSHOT.war, session-invalidation-src.zip
>
>
> When a request is being processed, and another concurrent request invalidates the session, invalidation is not reflected in the first request, i.e.: calling HttpServletRequest#isRequestedSessionIdValid() returns true. But trying to get any request attribute shows that the request is effectively destroyed. The same happens when the session expires after initiating the request.
> Related to WFLY-7568 and probably also to WFLY-6744



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)