Bug 808849 - [EAP6 Discovery fails for both Standalone and Domain modes
Summary: [EAP6 Discovery fails for both Standalone and Domain modes
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.3
Hardware: Unspecified
OS: Linux
urgent
urgent vote
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-01 10:07 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-02 14:34:42 UTC


Attachments (Terms of Use)
agent log with discovery failures (277.42 KB, application/octet-stream)
2012-04-01 10:07 UTC, Libor Zoubek
no flags Details

Description Libor Zoubek 2012-04-01 10:07:46 UTC
Created attachment 574312 [details]
agent log with discovery failures

Description of problem: since Build Number: 1202a18, agent fails do discover both domain and standalone EAP6 instances.


Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: 1202a18
EAP6 Beta1

How reproducible:always


Steps to Reproduce:
1.standup EAP6 in domain & standalone modes
2.check discovery queue contains both servers

  
Actual results: agent does not discover servers, see attached log for details

error for Domain discovery :  

Operation{operation='read-attribute', address=Address{path: }, additionalProperties={name=name, include-defaults=true}} failed with 500 (Internal Server Error) - response body was [{"outcome" : "failed", "failure-description" : "JBAS014792: Unknown attribute name", "rolled-back" : true}].

error for standalone discovery: 

/ (Is a directory)


Expected results:servers are discovered

Comment 1 Ian Springer 2012-04-02 14:34:42 UTC
Autodiscovery of both standalone servers and host controllers is working for me. I'm using HEAD of RHQ master and EAP6 ER4.1. 

jboss-as-7.JBossAS7 Host Controller: Starting discovery...
jboss-as-7.JBossAS7 Host Controller: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.as.host-controller|match=.*], name=[HostController]], process=[process: pid=[25634], name=[/usr/java/jdk1.6.0_30/jre/bin/java], ppid=[25610]]
jboss-as-7.JBossAS7 Host Controller: key=[/tmp/jboss-as-6.0.0.ER4/domain], name=[domain JBoss EAP 6 Domain Controller], version=[EAP 6.0.0.ER4], description=[Domain controller for a JBoss Enterprise Application Platform 6 domain]
jboss-as-7.JBossAS7 Host Controller: Done.

jboss-as-7.JBossAS7 Standalone Server: Starting discovery...
jboss-as-7.JBossAS7 Standalone Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.as.standalone|match=.*], name=[StandaloneAS]], process=[process: pid=[25503], name=[/usr/java/jdk1.6.0_30/jre/bin/java], ppid=[25437]]
jboss-as-7.JBossAS7 Standalone Server: key=[/tmp/jboss-as-6.0.0.ER4/standalone], name=[standalone EAP], version=[EAP 6.0.0.ER4], description=[Standalone JBoss Enterprise Application Platform 6 server]
jboss-as-7.JBossAS7 Standalone Server: Done.

Please give it another try with EAP6 ER4.1.

Comment 2 Libor Zoubek 2012-04-02 18:57:41 UTC
yes, it works with recent master build and EAP6 ER4.1


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