[jboss-jira] [JBoss JIRA] (WFLY-6514) DistributableSingleSignOn register an SessionIdChangeListener for each SSO session

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-6514:
-------------------------------
    Component/s: Clustering


> DistributableSingleSignOn register an SessionIdChangeListener for each SSO session
> ----------------------------------------------------------------------------------
>
>                 Key: WFLY-6514
>                 URL: https://issues.jboss.org/browse/WFLY-6514
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, Web (Undertow)
>    Affects Versions: 10.0.0.Final
>            Reporter: Juan AMAT
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> During performance testing on our app we noticed an continuous increase of CPU utilization while the load was constant. 
> In turns out that for each session an undertow SessionListener was registered at login and was never unregistered (request.logout or session.invalidate).
> As a result all the operations on undertow SessionListeners are taking more CPU every time a listener is added as we loop over those listeners.
> First of all we should register only one (if needed) such SessionListener per webapp.
> But even in the current implementation, the listener was not unregistered when request.logout was called.
> It is unregistered when session.invalidate is called but then this is not the same listener that is provided and thus nothing is done.



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