[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-478) Session draining always takes maximum configured timeout since listener is always notified before session is removed
RH Bugzilla Integration (JIRA)
issues at jboss.org
Wed Jan 18 07:52:01 EST 2017
[ https://issues.jboss.org/browse/MODCLUSTER-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13350363#comment-13350363 ]
RH Bugzilla Integration commented on MODCLUSTER-478:
----------------------------------------------------
Petr Penicka <ppenicka at redhat.com> changed the Status of [bug 1314792|https://bugzilla.redhat.com/show_bug.cgi?id=1314792] from VERIFIED to CLOSED
> 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
(v7.2.3#72005)
More information about the mod_cluster-issues
mailing list