[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-478) Session draining always takes maximum configured timeout since listener is always notified before session is removed

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated MODCLUSTER-478:
--------------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 1.2.12.Final
                   1.3.3.Final
       Resolution: Done


Merged 1.3.x and 1.2.x branches now.

> Session draining always takes maximum configured timeout since listener is always notified before session is removed
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-478
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-478
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Core & Container Integration (Java)
>    Affects Versions: 1.2.11.Final, 1.3.1.Final
>         Environment: -JBoss EAP 6
>            Reporter: Aaron Ogburn
>            Assignee: Radoslav Husar
>             Fix For: 1.2.12.Final, 1.3.3.Final
>
>
> mod_cluster session draining does not properly end when an active session is invalidated.  The NotifyOnDestroySessionListener is not invoked because it is not properly added.  That listener is added as a ApplicationLifecycleListeners, but JBossWeb 7 invokes ApplicationSessionLifecycleListeners instead upon session expiration.



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