Bug 814243 - [eap6] harmless error in agent.log when discovery runs
Summary: [eap6] harmless error in agent.log when discovery runs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin
TreeView+ depends on / blocked
 
Reported: 2012-04-19 12:55 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 19:20:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2012-04-19 12:55:39 UTC
Description of problem: I am getting harmless errors in agent.log when discovery runs. I am not able to guess what does it mean.

Main reason why I create this BZ is, that I'd like to enable agent.log checking, that seeks for error line when each test runs, I hope it will help detecting issues not caught by assertions.

Could these be removed?

Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: a5e442c
EAP6 ER5

How reproducible:always


Steps to Reproduce:
1.start agent on host where both domain & stanadlone EAP runs
2.run manual autodiscovery on agent
3.check log
  
Actual results: This appears in agent.log

ERROR [ResourceDiscoveryComponent.invoker.daemon-11] (rhq.modules.plugins.jbossas7.HostControllerDiscovery)- / (Is a directory)
ERROR [ResourceDiscoveryComponent.invoker.daemon-12] (rhq.modules.plugins.jbossas7.StandaloneASDiscovery)- / (Is a directory)

Comment 1 Heiko W. Rupp 2012-05-15 10:55:14 UTC
I think this can be closed - there have been lots of refactorings and I can't see that in the logs.

Comment 2 Heiko W. Rupp 2013-09-01 19:20:00 UTC
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.


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