[
https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181509#comment-15181509
]
Roman Shtykh commented on IGNITE-2710:
--------------------------------------
Thank you!
1) methods are guarded according to the HttpSession specs. Probably the only
left are _s/getMaxInactiveInterval()_ and _getId()_ but specs don't say how it
should behave when the session is invalid, it says they must return a value.
All the rest are deprecated and call guarded methods.
http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpSession.html
2) I guess it's the same IGNITE-810 which doesn't work for _testRestarts()_
> 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
(v6.3.4#6332)
