[jboss-jira] [JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout

RH Bugzilla Integration (JIRA) issues at jboss.org
Wed Jan 18 07:52:01 EST 2017


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

RH Bugzilla Integration commented on WFLY-6294:
-----------------------------------------------

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
> --------------------------------------------------------
>
>                 Key: WFLY-6294
>                 URL: https://issues.jboss.org/browse/WFLY-6294
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.Final
>            Reporter: Aaron Ogburn
>            Assignee: Radoslav Husar
>            Priority: Blocker
>              Labels: downstream_dependency
>             Fix For: 10.1.0.CR1, 10.1.0.Final
>
>
> The mod_cluster session drain wait is not ending as expected.  mod_cluster adds a session listener to be notified of session destruction.  That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active.  Thus, this drain loop doesn't end after the notify because it still sees the active session:
> {code}
>                 while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) {
>                     ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context);
>                     listener.wait(noTimeout ? 0 : timeout);
>                     current = System.currentTimeMillis();
>                     timeout = end - current;
>                     remainingSessions = context.getActiveSessionCount();
>                 }
> {code}
> Can the listeners be invoked when the session is fully removed and no longer considered active?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list