mod_cluster session draining does not work
Environment
- JBoss Enterprise Application Platform (EAP) 6.x
Issue
- We use mod_cluster and its session draining. mod_cluster always takes the full stop-context-timeout to drain sessions even though all sessions certainly were invalidated before then.
Resolution
- Apply the 6.4.8 CP
Root Cause
- This content is not included.BZ-1314792
- Content from issues.jboss.org is not included.MODCLUSTER-478
- mod_cluster uses a session listener to be notified when a session expires. That listener was not properly added so it was not invoked. But if that listener is invoked, mod_cluster would still see the session as active because the listener is invoked before sessions are removed. Thus, mod_cluster's session drain always takes the full amount of time.
- Content from issues.jboss.org is not included.WFLY-6294
SBR
Category
Tags
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.