In previous versions of JBoss EAP 6, using the `ModClusterService` stop or `stopContext` commands from the CLI interface failed to move a context to the STOPPED state after failing to drain the active sessions. This meant these commands were not viable for quickly stopping the context when desired (without draining). This issue has been resolved with an updated to the mod_cluster component.
Description of problem:
Using the ModClusterService stop or stopContext commands via CLI always fails to move a context to the STOPPED state after failing to drain the active sessions. So these commands then aren't very useful for quickly stopping the context when desired if you can't do it without draining.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup httpd/JBoss/mod_cluster and deploy a <distributable/> app on JBoss
2. Establish a session on this app
3. Call via cli:
And note that modcluster will try to drain the sessions, fail to do that within time, and then not stop the context (leaving it in a disabled state on httpd)
Session draining strategy isn't honored so stop commands usually don't actually stop contexts
Session draining strategy is honored so stop commands can be useful
Fixed per MODCLUSTER-404 so we need a component upgrade
Updating to mod_cluster-1.2.9.Final have fixed the issue.
Verified in EAP 6.3.0.ER7
- calling ./jboss-cli.sh --connect --controller=192.168.122.78:9999 --command="/subsystem=modcluster:stop()"
does not stop the context, present sessions are being kept
- calling the aforementioned causes an immediate failover to another node
This bug is shown as affecting and fixed in 6.3.0. Is this the case? It might not need a release note.
It needs a release note it was reported by a customer against 6.2.
Changed Version setting to 6.2 based on comment 5 (this will ensure it gets included in the 6.3.0 Release Notes)