Bug 845954 - exception in log during the first inventory of agent
Summary: exception in log during the first inventory of agent
Keywords:
Status: CLOSED DUPLICATE of bug 856845
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-06 09:27 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-22 00:01:19 UTC
Embargoed:

Attachments (Terms of Use)
exceotionResourceId0 (1.43 KB, text/x-log)
2012-08-06 09:27 UTC, Armine Hovsepyan 		no flags Details
View All

Description Armine Hovsepyan 2012-08-06 09:27:12 UTC 
Created attachment 602470 [details]
exceotionResourceId0

Description of problem:
During the first Inventory of the agent on clean server it shows Null Pointer exception on logs, that "Resource component container could not be retrieved for resource: 0".

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

How reproducible:
always

Steps to Reproduce:
1. Install jon server
2. start agent
3. inventory the whole agent to server
  
Actual results:
exceptions in log

Expected results:
no exceptions in log

Additional info:
Error part of the log is attached
Comment 1 Charles Crouch 2012-11-20 20:33:42 UTC 
Setting sev. versus priority
Comment 2 mark yarborough 2012-11-20 20:45:37 UTC 
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
Comment 3 Larry O'Leary 2012-11-22 00:01:19 UTC 
Although this is the earlier bug, closing this one as the dupe due to the later containing complete details and existing on the product and project.

*** This bug has been marked as a duplicate of bug 856845 ***
Note You need to log in before you can comment on or make changes to this bug.