[jboss-jira] [JBoss JIRA] (WFLY-5473) Session.invalidate() does not invalidate SSO context for non-distributable applications

Ladislav Thon (JIRA) issues at jboss.org
Fri Dec 11 02:31:00 EST 2015


    [ https://issues.jboss.org/browse/WFLY-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140025#comment-13140025 ] 

Ladislav Thon commented on WFLY-5473:
-------------------------------------

[~rjanik] My understanding is that if a fix is merged, but there's no release with a fix, correct JIRA state is _Resolved_. If a fix has hit the release, the correct JIRA state is _Closed_. In any case, if you can still reproduce the problem on current WildFly master, neither _Resolved_ nor _Closed_ is a correct JIRA state.

> Session.invalidate() does not invalidate SSO context for non-distributable applications
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-5473
>                 URL: https://issues.jboss.org/browse/WFLY-5473
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, Web (Undertow)
>            Reporter: Richard Janík
>            Assignee: Paul Ferraro
>            Priority: Blocker
>             Fix For: 10.0.0.CR5
>
>
> See "Steps to Reproduce" for detailed description.
> According to my limited knowledge, this was also the core issue in https://bugzilla.redhat.com/show_bug.cgi?id=924456 which has been dispatched as a one-off to a customer. Thus, I'm setting the priority to blocker as this is a regression against 6.4.x. No exceptions have been observed in the server output however.
> Adding Clustering component as I've been trying this with standalone-ha.xml and BZ 924456 relates to clustering.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jboss-jira mailing list