Bug 1314792 - [GSS](6.4.z) mod_cluster session drain does not end
Summary: [GSS](6.4.z) mod_cluster session drain does not end
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: mod_cluster
Version: 6.4.6
Hardware: All
OS: Unspecified
Target Milestone: CR1
: EAP 6.4.8
Assignee: baranowb
QA Contact: Michal Karm Babacek
Depends On:
Blocks: 1321090 1324903 1258395 eap648-payload
TreeView+ depends on / blocked
Reported: 2016-03-04 13:57 UTC by Aaron Ogburn
Modified: 2019-10-10 11:26 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-01-17 12:34:22 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-3969 0 Blocker Verified (7.0.z) Session draining always takes maximum configured timeout 2018-05-09 05:16:45 UTC
Red Hat Issue Tracker MODCLUSTER-478 0 Major Resolved Session draining always takes maximum configured timeout since listener is always notified before session is removed 2018-05-09 05:16:44 UTC
Red Hat Issue Tracker WFLY-6294 0 Blocker Closed Session draining always takes maximum configured timeout 2018-05-09 05:16:44 UTC
Red Hat Knowledge Base (Solution) 2186601 0 None None None 2016-03-04 13:59:25 UTC

Description Aaron Ogburn 2016-03-04 13:57:42 UTC
Description of problem:

mod_cluster uses a session listener to be notified when a session expires during session draining shutdown waits. That listener is not properly added so it is not invoked.

But even if it were invoked, it would not allow the session drain to end.  JBossWeb invokes session listeners before the session is removed, so after the listener is invoked, mod_cluster still sees an active session and continues to wait.

mod_cluster's session drain needs to be redesigned some or JBossWeb needs to fire session listeners after the session is removed.

How reproducible:


Steps to Reproduce:
1. Run ha profile with an increased session drain stop timeout:

            <mod-cluster-config advertise-socket="modcluster" stop-context-timeout="300" connector="default" session-draining-strategy="ALWAYS">

2. create a session in an app
3. stop jboss
4. invalidate that session
5. note shutdown drain wait doesn't end

Actual results:

Session draining does not end when all sessions are invalidated.

Expected results:

Session draining does end when all sessions are invalidated.

Comment 2 Mike McCune 2016-03-28 22:44:25 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Michal Karm Babacek 2016-04-01 00:20:34 UTC
I confirm that f38dce459 1.2.12.Final-SNAPSHOT upstream mod_cluster fixes the issue, although we need a productized artifact...

Comment 9 Michael Cada 2016-05-10 08:11:12 UTC
Verified with EAP 6.4.8.CP.CR2

Comment 10 Petr Penicka 2017-01-17 12:34:22 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Note You need to log in before you can comment on or make changes to this bug.