Red Hat Bugzilla – Bug 822250
Tomcat6 mod_cluster config file (JON)
Last modified: 2018-03-06 15:35:31 EST
Created attachment 585050 [details]
Scnreeshot of ModCluster Config property
Description of problem:
Mod_cluster config file error on Inventory Connections screen for mod_cluster
Version-Release number of selected component (if applicable):
EWS v1.0.2 Apache/Tomcat6
Configure EWS Tomcat6 for mod_cluster. Boot the server and import the EWS Tomcat6 server into JON. A red exclamation will appear next to the mod_cluster=>Inventory=>Connection Settings for ModCluster Config file.
Attempted to configure this file as the Tomcat6 server.xml and exclamation error still remains.
For EAP instances imported, this file is set to "mod_cluster-jboss-beans.xml".
Steps to Reproduce:
1. Configure EWS Tomcat6 for mod_cluster.
2. Boot EWS Tomcat6 instance.
3. Import instance into JON.
4. View connection settings for mod_cluster on the instance.
per BZ triage 5/21/2012 (asantos, loleary, ccrouch, mfoley)
Needs EWS tracker bug.
Per 3.1.2 triage with loleary, mfoley, ccrouch, asantos: Okay to move to JON 3.2.
Note that modcluster listener breaks the storeconfig (the server.xml is broken after changing any thing in the tomcat configuration).
(In reply to Jean-frederic Clere from comment #6)
the server.xml issue has been fixed in EWS2.1.0 ER4.
I am going to look for the issue.
Looks like the JON mod_cluster plugin does not support Tomcat servers
I created a mojo document to establish the different solutions there is to fix the bug : https://mojo.redhat.com/docs/DOC-998620
Please feel free to give your opinion about it.
I wrote some code to add support for Tomcat Servers. It's currently in pull request : https://github.com/rhq-project/rhq/pull/158
in master https://github.com/rhq-project/rhq/commit/32969c92ac28c374ef52e77fde61af0519533414