[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:comment-tabpanel&focusedCommentId=13181626#comment-13181626 ] 

Radoslav Husar commented on MODCLUSTER-478:
-------------------------------------------

Submitted PR to fix the broken notification schema https://github.com/modcluster/mod_cluster/pull/170

The jbossweb7-specifics should be solved too, but ^ mitigates the problem to minimum.

For WildFly part of this and specifics see comment https://issues.jboss.org/browse/WFLY-6294?focusedCommentId=13181624&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13181624

> 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)
>         Environment: -JBoss EAP 6
>            Reporter: Aaron Ogburn
>            Assignee: Radoslav Husar
>
> 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)