Bug 1098576
Summary: | ModClusterService stop commands are always draining sessions | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Aaron Ogburn <aogburn> |
Component: | mod_cluster | Assignee: | Jean-frederic Clere <jclere> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michal Karm Babacek <mbabacek> |
Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | kkhan, mbabacek, smumford |
Target Milestone: | ER6 | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-28 15:44:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1101681, 1107551 | ||
Bug Blocks: |
Description
Aaron Ogburn
2014-05-16 15:07:55 UTC
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 mod_cluster 1.2.8 - 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 mod_cluster 1.2.9 - 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. |