Bug 1127356

Summary: ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-resource") failed
Product: [JBoss] JBoss Operations Network Reporter: Matt Mahoney <mmahoney>
Component: Core ServerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: hrupp, mmahoney
Target Milestone: DR02   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-03 18:23:04 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:
Attachments:
Description Flags
Server.log none

Description Matt Mahoney 2014-08-06 18:11:01 UTC
Created attachment 924554 [details]
Server.log

Description of problem:
Error in server.log file after clean install and server start:

10:49:46,987 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-resource") failed - address: ([("subsystem" => "web")]) - failure description: "JBAS014807: Management resource '[(\"subsystem\" => \"web\")]' not found"


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

How reproducible:


Steps to Reproduce:
1. Install and start JON
2.
3.

Actual results:
Errors in server.log after clean install/start.

Expected results:
Should be zero silent errors in server.log

Additional info:

Comment 1 Heiko W. Rupp 2014-08-26 12:39:06 UTC
That is very obviously a message of the underlying EAP.

JON startup needs to determine if the web connector is already deployed or not and does this my trying to read the resource. Unfortunately EAP is logging a simple "not found" as a severe failure, as it is too stupid internally to differentiate between a 404 and 500 error code and always returns a 500 one.

Proposing to close this with won't fix.

Comment 2 Red Hat Bugzilla 2023-09-14 02:45:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days