Simeon Pinder created AS7-4880:
----------------------------------
Summary: modcluster subsystem operations(stop*/enable*/disable*-context) on
http instance stop working after/with mod_cluster_manager use
Key: AS7-4880
URL:
https://issues.jboss.org/browse/AS7-4880
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.2.Final (EAP)
Environment: ER8
Reporter: Simeon Pinder
Assignee: Alexey Loubyansky
With a modcluster setup if you are using the cli subsystem (stop*/enable*/disable*
-context) operations to modify contexts successfully and then you or anyone else uses the
http://<ip address>:<port>/mod_cluster_manager to enable/disable any contexts
then continued operations by cli stop working. The only fix in this situation is to
restart the http instance which is pretty bad.
It appears that the two mechanism to communicate with the http modcluster manager clobber
each other in some way with the cli subsystem loosing the ability to make changes.
Additionally we should add something to the release notes suggesting to disable/deprecate
the usage of mod_cluster_manager. However this should be resolved more completely because
as7 subsystem commands from a completely valid setup simply won't work with no
feedback.
Note: mod_cluster_manager commands and operations continue happily.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira