ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shtykh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-2710) Session not unbind from current request after invoking request.getSession().invalidate()
Date Mon, 29 Feb 2016 06:46:18 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158567#comment-15158567

Roman Shtykh edited comment on IGNITE-2710 at 2/29/16 6:45 AM:

Attributes are correctly nullified, but after the current session is invalidated, a new one
with a different id has to be created (and that does not happen).

Another problem is a bunch of methods should throw IllegalStateException on invalidaded session

was (Author: roman_s):
Thank you!
It invalidates the session's variables (they are correctly nullified), but _getId()_ (and
some other methods http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpSession.html)
should throw {{java.lang.IllegalStateException}}

> Session not unbind from current request after invoking request.getSession().invalidate()
> ----------------------------------------------------------------------------------------
>                 Key: IGNITE-2710
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2710
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.5.0.final
>         Environment: java8, tomcat8
>            Reporter: YuxuanWang
>            Assignee: Roman Shtykh
>              Labels: community, session, user
>             Fix For: 1.6
> System.out.println(request.getSession().getId());
> request.getSession().invalidate();
> System.out.println(request.getSession().getId());
> getSession() although return the same session after the invalidation.

This message was sent by Atlassian JIRA

View raw message