Bug 717761 - JBoss AS6 Discovery Error
Summary: JBoss AS6 Discovery Error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugin Container
Version: 4.1
Hardware: Unspecified
OS: Linux
low
unspecified vote
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-29 19:41 UTC by Stefan Negrea
Modified: 2013-08-06 00:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:32:03 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Stefan Negrea 2011-06-29 19:41:42 UTC 
Description of problem:
Cannot discover JBoss AS6 using the plugin container. 

Version-Release number of selected component (if applicable):
4.1.0-SNAPSHOT

How reproducible:
Every time.

Steps to Reproduce:
1. Run JBoss AS6 on the local machine
2. Run unit tests to discover servers with the plugin container.
3. Notice that JBoss AS6 does not get discovered. See the errors in the attached log.
  
Actual results:
Error while discovering JBoss AS6 instances.

Expected results:
Successful discovery of the JBoss AS6 instance


Additional info:
Used:
- JBoss AS6 from jboss.org
- Fedora-14
- mod_cluster enabled and connected to the http server
Comment 1 Ian Springer 2011-06-29 20:00:17 UTC 
I am curious if step 2) (running in the unit test env) is the cause of the issue. Can you try running an Agent on the same machine and see if it discovers the AS6 instance?
Comment 2 Stefan Negrea 2011-10-10 05:03:51 UTC 
This defect has been fixed by Ian, the code change is in master. I tested the fix through the mod_cluster integration tests. 

To manually verify the fix, please use JBoss AS6 final in conjunction with an additional JMX based plugin (mod_cluster is a good example). If the additional JMX based service is discovered and functional then the issue is fixed.
Comment 3 Mike Foley 2011-10-11 14:21:30 UTC 
verified
Comment 4 Mike Foley 2012-02-07 19:32:02 UTC 
marking VERIFIED BZs to CLOSED/CURRENTRELEASE
Comment 5 Mike Foley 2012-02-07 19:32:03 UTC 
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.