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:
This is blocked by issue : https://issues.jboss.org/browse/AS7-4847
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
These commits have been in JON release builds for a while, pushing to ONQA
Removing target as this is not JBoss ON specific. The downstream bug is Bug 828893.
Is in RHQ for a long time, closing.