Bug 651832

Summary:	JBossas5: auto discovery of JBossAS5 fails after uninventory.
Product:	[Other] RHQ Project	Reporter:	Sudhir D <sdharane>
Component:	Plugins	Assignee:	Lukas Krejci <lkrejci>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.0	CC:	lkrejci, rtimaniy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-24 01:07:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	616081

Description Sudhir D 2010-11-10 12:10:10 UTC

Description of problem:
The auto discovery of jbossas5 server failed after I uninventory, it never auto discovered the jbossAS5 server.

Version-Release number of selected component (if applicable):
rhq-server-3.0.1-SNAPSHOT build# 8469bdd

How reproducible:
Always

Steps to Reproduce:
1. Install rhq-server and rhq-agent where JBossAS5 server is running. Ensure that jboss-as-5 plugin is present.
2. Import the auto discovered JBossAS5 server.
3. Uninventory the JBossAS5 server.
4. Restart both rhq server and agent and JBossAS5 server.
  
Actual results:
JBossAS5 server is not auto discovered.

Expected results:
JBossAS5 server should be auto discovered.

Additional info:
I can see that the pid of the JBossAS5 server picked up in log but it just does not show up in the auto discovery queue.

Comment 1 Lukas Krejci 2010-11-18 19:38:30 UTC

I could not reproduce this with the latest RHQ build.

Could you please try once more and if you are still experiencing this, could you provide as much detail about the RHQ server and agent installs as well as the AS5 server as possible?

Comment 2 Charles Crouch 2010-12-13 23:34:59 UTC

Pushing to ON_QA to retest

Comment 3 Rajan Timaniya 2010-12-14 10:24:09 UTC

Tested on JON 2.4.1 build #41 (build number: 10963:e46b3e2)

I couldn't reproduce this with JON-241 build #41.

I found NoSuchMethodException in agent.log during bug verification and filed separate bug for it (bug #662978).

Comment 4 Corey Welton 2011-05-24 01:07:49 UTC

Bookkeeping - closing bug - fixed in recent release.