Bug 642732
Summary: | Web Application Context Availability reports DOWN when JBoss Web is started with host name other than localhost | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Larry O'Leary <loleary> |
Component: | Plugins | Assignee: | Stefan Negrea <snegrea> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.0.0 | CC: | lkrejci, snegrea |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-02 07:14:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 625146 |
Description
Larry O'Leary
2010-10-13 16:47:35 UTC
Missed this in the description but here is the error you see in the agent log if debug logging is enabled: Failed to find [ComponentType{type=MBean, subtype=WebApplicationManager}] ManagedComponent named [jboss.web:host=my.real.hostname.redhat.com,path=/,type=Manager] This issue appears to be a problem in ProfileService of EAP/AS. Logged JBPAPP-5260 in upstream. The missing componentType from ProfileService is due to ${JBOSS_HOME}/server/${JBOSS_CONF}/deploy/profileservice-jboss-beans.xml scoping the Manager bean to a specific host: <bean name="WarManagedDeploymentFactory" class="org.jboss.profileservice.management.ProxyManagedDeploymentFactory"> <property name="factoryName">War</property> <property name="defaultViewUse">STATISTIC</property> <property name="rootMOPatterns"> <set elementClass="org.jboss.profileservice.management.ProxyDeploymentInfo"> <!-- Manager --> <bean class="org.jboss.profileservice.management.ProxyDeploymentInfo"> <property name="compType">MBean</property> <property name="compSubtype">WebApplicationManager</property> <property name="pattern">jboss.web:host=localhost,type=Manager,*</property> <property name="nameBuilder"> <inject bean="WarManagerMBeanDeploymentNameBuilder"/> </property> </bean> <!-- WebModule --> <bean class="org.jboss.profileservice.management.ProxyDeploymentInfo"> ... Specifically: <property name="pattern">jboss.web:host=localhost,type=Manager,*</property> Changing this to: <property name="pattern">jboss.web:type=Manager,*</property> Resolves this issue and additionally allows a WebModule deployed to one or more vhosts to appear in ProfileService as well. Here is a sed command which will fix this: JBOSS_HOME=/opt/jboss/eap/jboss-eap-5.1.0/jboss-as JBOSS_CONF=default sed -i.orig 's/^.*<property name="pattern">jboss\.web:.*,type=Manager,\*<\/property>$/ <property name="pattern">jboss.web:type=Manager,*<\/property>/g' "${JBOSS_HOME}/server/${JBOSS_CONF}/deploy/profileservice-jboss-beans.xml" The AS fix has been committed upstream on AS 6.0 and also will be included in EAP post 5.1 (i.e. 5.1.1, or > 5.1). I just tested the reported problem with EAP5.1.1 and I cannot replicate it. The issues has been resolved on EAP side. This BZ does not require any change in RHQ code. Please retest. Confirmed that this issue seems to have been fixed in EAP 5.1.1. The context is shown as unavailable in EAP 5.1.0 but is correctly shown as UP in EAP 5.1.1 with identical configuration. Putting this to verified as there are no code changes on our side. Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago. |