[ https://issues.jboss.org/browse/WFLY-332?page=com.atlassian.jira.plugin.s... ] rafael liu commented on WFLY-332: --------------------------------- Rodaslav, looks like you are talking about mod_cluster end. What I tried to say is that when doing a undeploy/redeploy through WildFly it would be useful to set a sessionDrainingStrategy for that operation only (rather than once, system wide). In case #1, what I see is JBoss throwing an exception: 15:46:17,325 WARN [org.jboss.modcluster] (ServerService Thread Pool -- 137) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/myapp within 10,000000.1 seconds 15:46:17,327 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 137) MODCLUSTER000021: All pending requests drained from default-host:/myapp in 10,002000.1 seconds In case #2, I don't see how to skip session draining in JBoss/WildFly. It always seems to enforce this behavior, am I wrong? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira