Bug 829058

Summary: No handler for read-resource at address in agent.log
Product: [JBoss] JBoss Operations Network Reporter: Viet Nguyen <vnguyen>
Component: Plugin -- JBoss EAP 6Assignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: medium    
Version: JON 3.1.0CC: hrupp, snegrea
Target Milestone: ---   
Target Release: JON 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-21 20:01:49 UTC Type: Bug
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: 707223    

Description Viet Nguyen 2012-06-05 20:56:24 UTC
Description of problem:

I'm seeing a lot of these warnings in agent.log

2012-06-05 16:46:23,457 WARN  [ResourceDiscoveryComponent.invoker.daemon-9] (rhq.modules.plugins.jbossas7.ASConnection)- We got a 500 with the following response body back: {"outcome" : "failed", "failure-description" : "JBAS014739: No handler for read-resource at address [(\"subsystem\" => \"modcluster\")]", "rolled-back" : true}

2012-06-05 16:46:23,581 WARN  [ResourceDiscoveryComponent.invoker.daemon-9] (rhq.modules.plugins.jbossas7.ASConnection)- We got a 500 with the following response body back: {"outcome" : "failed", "failure-description" : "JBAS014739: No handler for read-resource at address [(\"subsystem\" => \"connector\")]", "rolled-back" : true}


Version-Release number of selected component (if applicable):


How reproducible:

JON 3.1.CR2 + AS7 plugin + EAP6CR1

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Charles Crouch 2012-08-29 16:08:01 UTC
As per 8/20 triage 8/20 pushing to JON312

Comment 2 Stefan Negrea 2012-09-21 20:01:49 UTC
This is not an issue. The log entry is just saying that the subsystem or resource is not available in the respective inventoried EAP6 instance. The only way to know if a subsystem is available for management is to probe the server, and if the resource is not there the server responds with 500 error message. The plugin logs the EAP 6 response message and treats it as an indication that the resource is not there.

Not all the subsystem are available in a typical EAP6 instance. The users can preconfigure the server to only run the a subset of all available subsystem. Alternatively, users can avoid loading unused subsystem by starting the server using one of the pre-set configurations. Just as an example, the HA variation of the pre-set configuration is missing some subsystem present only on Full-HA configuration.