This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 823624

Summary: mod_cluster enable*/disable*/stop* not working across cluster members.
Product: [Other] RHQ Project Reporter: Simeon Pinder <spinder>
Component: PluginsAssignee: Simeon Pinder <spinder>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp, loleary
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 828893 (view as bug list) Environment:
Last Closed: 2013-12-07 10:07:53 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 707223, 828893    

Description Simeon Pinder 2012-05-21 13:52:04 EDT
Description of problem:
To execute enable*/disable*/start* operations the modcluster plugin requires access to the unique 'jvmRoute' identifier to be able to initiate execution on the appropriate RHQ resources.  Without it there is no way to uniquely identify which 'virtual-hosts' contain which 'contexts' reliably.

Version-Release number of selected component (if applicable):


How reproducible:
N/A

Steps to Reproduce:
1. Create modcluster cluster with two standalone AS7 instances on two different machines.
2. Deploy a web application to the cluster members, attempt to submit stop-context on the nodes. 
3.
  
Actual results:
Stop-Context only affects the contents of one host.

Expected results:
Able to issue Stop-Context commands to any of the node members.

Additional info:
Comment 1 Simeon Pinder 2012-05-21 13:54:52 EDT
This is blocked by issue : https://issues.jboss.org/browse/AS7-4847
Comment 3 Simeon Pinder 2012-06-04 12:46:48 EDT
This is not fixed because of the blocking bug, but the following commits to master and release/jon3.1.x respectively disables the functionality to that it is not available and users are less confused by operations they cannot execute.

master               release/jon3.1.x
633ef4fb             e1d1fe28a51
89bf8dfc             3ad5f3a1668
Comment 4 Charles Crouch 2012-06-05 10:43:48 EDT
These commits have been in JON release builds for a while, pushing to ONQA
Comment 5 Larry O'Leary 2012-11-21 18:00:10 EST
Removing target as this is not JBoss ON specific. The downstream bug is Bug 828893.
Comment 6 Heiko W. Rupp 2013-12-07 10:07:53 EST
Is in RHQ for a long time, closing.