Bug 1015719 - DiscoveryBossBean: Unknown resource type error, unclear from which agent the error is from
Summary: DiscoveryBossBean: Unknown resource type error, unclear from which agent the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.10
Assignee: Libor Zoubek
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 23:01 UTC by Elias Ross
Modified: 2015-11-02 00:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:32:35 UTC
Embargoed:


Attachments (Terms of Use)

Description Elias Ross 2013-10-04 23:01:36 UTC
Description of problem:

Seen in the log file:

22:56:28,549 ERROR [org.rhq.enterprise.server.discovery.DiscoveryBossBean] (http-/0.0.0.0:7080-155) Reported resource [Resource[id=0, uuid=27d8a8a4-1db7-4757-99e7-6d690184f592, type={JBossAS7}Authentication (Classic), key=subsystem=security,security-domain=RHQRESTSecurityDomain,authentication=classic, name=Authentication (Classic), parent=RHQRESTSecurityDomain]] has an unknown type [ResourceType[id=0, name=Authentication (Classic), plugin=JBossAS7, category=Service]]. The Agent most likely has a plugin named 'JBossAS7' installed that is not installed on the Server. Resource will be ignored...

It would be nice to know which agent is reporting this error.

I can't find the resource as the UUID doesn't exist and the id is null.


Additional info:

The server does have the JBossAS7 plugin installed, so this is very confusing.

Comment 1 Libor Zoubek 2014-02-25 19:56:37 UTC
in master
commit ad13c7ec68b1667e40191aaec2683d5d68a9b692
Author: Libor Zoubek <lzoubek>
Date:   Tue Feb 25 20:52:59 2014 +0100

    [BZ 1015719] DiscoveryBossBean: Unknown resource type error, unclear from
    which agent the error is from

    Log message changed to include agent details

Comment 2 Heiko W. Rupp 2014-04-23 12:32:35 UTC
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.


Note You need to log in before you can comment on or make changes to this bug.