Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 1.2.12.Final, 1.3.3.Final
Affects Version/s: 1.2.11.Final, 1.3.1.Final
Component/s: Core + SPIs
Labels:
None

Steps to Reproduce:
Hide

-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">

-create a session in an app
-stop jboss
-invalidate that session
-note shutdown drain wait doesn't end
Show
-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" > -create a session in an app -stop jboss -invalidate that session -note shutdown drain wait doesn't end
Git Pull Request:
https://github.com/modcluster/mod_cluster/pull/171, https://github.com/modcluster/mod_cluster/pull/170, https://github.com/modcluster/mod_cluster/pull/166
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1314792, https://bugzilla.redhat.com/show_bug.cgi?id=1321090, https://bugzilla.redhat.com/show_bug.cgi?id=1324903

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.

blocks

JBEAP-3969 (7.0.z) Session draining always takes maximum configured timeout

Verified

WFLY-6294 Session draining always takes maximum configured timeout

Closed

Assignee:: Radoslav Husar

Reporter:: Aaron Ogburn

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2016/02/26 2:55 PM

Updated:: 2021/10/24 6:14 AM

Resolved:: 2016/03/29 12:33 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates