[
https://jira.jboss.org/jira/browse/JOPR-103?page=com.atlassian.jira.plugi...
]
corey welton updated JOPR-103:
------------------------------
For what it's worth, these are the tomcat rpms installed by RHN Satellite. At this
moment, not sure how/if they differ from standard RHEL Tomcat RPMs.
[root@rlx-0-12 ~]# rpm -qa|grep tomcat
tomcat5-5.5.23-0jpp.7.el5_2.1
tomcat5-common-lib-5.5.23-0jpp.7.el5_2.1
tomcat5-jasper-5.5.23-0jpp.7.el5_2.1
tomcat5-jsp-2.0-api-5.5.23-0jpp.7.el5_2.1
tomcat5-servlet-2.4-api-5.5.23-0jpp.7.el5_2.1
tomcat5-server-lib-5.5.23-0jpp.7.el5_2.1
If they exist in a similar state in RHEL -- i.e., they go the same place -- we may have a
bigger issue than simply Satellite (and probably Spacewalk) namespace overlap.
EWS/Tomcat detection logic ambiguous (namespace collision?)
-----------------------------------------------------------
Key: JOPR-103
URL:
https://jira.jboss.org/jira/browse/JOPR-103
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: corey welton
Priority: Blocker
1. Install RHN Satellite on a box
2. Install JON Agent on same box; begin monitoring.
3. View inventory, noting "JBoss EWS Tomcat" in the inventory.
4. Go to Inventory > Connection tab for this tomcat server
5. Observe "Installation Home" value
Current results:
The value for "Installation home" used by RHN Satellite is
"/usr/share/tomcat5". This is the string that is used to identify EWS.
However, this is not an EWS Tomcat install. End result: This is detected/displayed as
"JBoss EWS Tomcat" in jopr, even though it actually isn't.
Expected results:
a non EWS-labelled value returned
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira